What is GHSA-VX74-F528-FXQG?

GHSA-VX74-F528-FXQG is a high-severity uncontrolled resource consumption vulnerability in github.com/nghttp2/nghttp2 (go), affecting versions < 1.57.0. It is fixed in 1.57.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-VX74-F528-FXQG?

GHSA-VX74-F528-FXQG has a CVSS score of 7.5 (High). 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 github.com/nghttp2/nghttp2 are affected by GHSA-VX74-F528-FXQG?

github.com/nghttp2/nghttp2 (go) versions < 1.57.0 is affected.

Is there a fix for GHSA-VX74-F528-FXQG?

Yes. GHSA-VX74-F528-FXQG is fixed in 1.57.0. Upgrade to this version or later.

Is GHSA-VX74-F528-FXQG exploitable, and should I be worried?

Whether GHSA-VX74-F528-FXQG 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.

What actually determines whether GHSA-VX74-F528-FXQG 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 GHSA-VX74-F528-FXQG?

Upgrade github.com/nghttp2/nghttp2 to 1.57.0 or later.

GHSA-VX74-F528-FXQG in github.com/nghttp2/nghttp2

Q: How severe is GHSA-VX74-F528-FXQG?

GHSA-VX74-F528-FXQG has a CVSS score of 7.5 (High). 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.

Q: Which versions of github.com/nghttp2/nghttp2 are affected by GHSA-VX74-F528-FXQG?

github.com/nghttp2/nghttp2 (go) versions < 1.57.0 is affected.

Q: Is there a fix for GHSA-VX74-F528-FXQG?

Yes. GHSA-VX74-F528-FXQG is fixed in 1.57.0. Upgrade to this version or later.

Q: Is GHSA-VX74-F528-FXQG exploitable, and should I be worried?

Whether GHSA-VX74-F528-FXQG 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.

Q: What actually determines whether GHSA-VX74-F528-FXQG 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.

Q: How do I fix GHSA-VX74-F528-FXQG?

Upgrade github.com/nghttp2/nghttp2 to 1.57.0 or later.

Summary

github.com/nghttp2/nghttp2 has HTTP/2 Rapid Reset

Workarounds

If upgrading to nghttp2 v1.57.0 is not possible, implement nghttp2_on_frame_recv_callback, and check and count RST_STREAM frames. If excessive number of RST_STREAM are received, then take action, such as dropping connection silently, or call nghttp2_submit_goaway and gracefully terminate the connection.

References

The following commit mitigates this vulnerability:

https://github.com/nghttp2/nghttp2/commit/72b4af6143681f528f1d237b21a9a7aee1738832

Impact

Rapidly creating and cancelling streams (HEADERS frame immediately followed by RST_STREAM) without bound cause denial of service.

See https://www.cve.org/CVERecord?id=CVE-2023-44487 for details.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-VX74-F528-FXQG has a CVSS score of 7.5 (High). 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 (1.57.0); upgrading removes the vulnerable code path.

Affected versions

github.com/nghttp2/nghttp2 (< 1.57.0)

Security releases

github.com/nghttp2/nghttp2 → 1.57.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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

nghttp2 v1.57.0 mitigates this vulnerability by default.

Frequently Asked Questions

What is GHSA-VX74-F528-FXQG? GHSA-VX74-F528-FXQG is a high-severity uncontrolled resource consumption vulnerability in github.com/nghttp2/nghttp2 (go), affecting versions < 1.57.0. It is fixed in 1.57.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-VX74-F528-FXQG? GHSA-VX74-F528-FXQG has a CVSS score of 7.5 (High). 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 github.com/nghttp2/nghttp2 are affected by GHSA-VX74-F528-FXQG? github.com/nghttp2/nghttp2 (go) versions < 1.57.0 is affected.
Is there a fix for GHSA-VX74-F528-FXQG? Yes. GHSA-VX74-F528-FXQG is fixed in 1.57.0. Upgrade to this version or later.
Is GHSA-VX74-F528-FXQG exploitable, and should I be worried? Whether GHSA-VX74-F528-FXQG 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 GHSA-VX74-F528-FXQG 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 GHSA-VX74-F528-FXQG? Upgrade github.com/nghttp2/nghttp2 to 1.57.0 or later.