golang.org/x/crypto

CVE-2025-58181

CVE-2025-58181 is a medium-severity allocation of resources without limits or throttling vulnerability in golang.org/x/crypto (go), affecting versions < 0.45.0. It is fixed in 0.45.0.

Key facts
CVSS score
5.3
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
golang.org/x/crypto
Fixed in
0.45.0
Disclosed
2025

Summary

SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.

Impact

What is allocation of resources without limits or throttling?

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Severity and exposure

CVE-2025-58181 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (0.45.0). Upgrading removes the vulnerable code path.

Affected versions

go

  • golang.org/x/crypto (< 0.45.0)

Security releases

  • golang.org/x/crypto → 0.45.0 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2025-58181 is reachable in your applications. Explore open-source security for your team.

See if CVE-2025-58181 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2025-58181 in your environment

Remediation advice

Upgrade golang.org/x/crypto to 0.45.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2025-58181

What is CVE-2025-58181?

CVE-2025-58181 is a medium-severity allocation of resources without limits or throttling vulnerability in golang.org/x/crypto (go), affecting versions < 0.45.0. It is fixed in 0.45.0. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

How severe is CVE-2025-58181?

CVE-2025-58181 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of golang.org/x/crypto are affected by CVE-2025-58181?

golang.org/x/crypto (go) versions < 0.45.0 is affected.

Is there a fix for CVE-2025-58181?

Yes. CVE-2025-58181 is fixed in 0.45.0. Upgrade to this version or later.

Is CVE-2025-58181 exploitable, and should I be worried?

Whether CVE-2025-58181 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2025-58181 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-58181?

Upgrade golang.org/x/crypto to 0.45.0 or later.

Stop the waste.
Protect your environment with Kodem.