How severe is GHSA-fxg5-wq6x-vr4w?

GHSA-fxg5-wq6x-vr4w has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fxg5-wq6x-vr4w?

GHSA-fxg5-wq6x-vr4w affects the following packages: golang.org/x/net (Go). Ecosystems affected: Go.

How do I fix GHSA-fxg5-wq6x-vr4w?

Update golang.org/x/net to 0.1.1-0.20221104162952-702349b0e862 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxg5-wq6x-vr4w is resolved across your whole dependency graph.

How do I detect GHSA-fxg5-wq6x-vr4w in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fxg5-wq6x-vr4w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fxg5-wq6x-vr4w?

O3 pinpoints whether GHSA-fxg5-wq6x-vr4w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fxg5-wq6x-vr4w actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-fxg5-wq6x-vr4w, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-fxg5-wq6x-vr4w?

GHSA-fxg5-wq6x-vr4w has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 76th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fxg5-wq6x-vr4w?

GHSA-fxg5-wq6x-vr4w is classified as CWE-444 (CWE-444). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fxg5-wq6x-vr4w published, and has it been updated?

GHSA-fxg5-wq6x-vr4w was published on January 14, 2023 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-fxg5-wq6x-vr4w: net (High 7.5)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk76th percentile+1.74%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹golang.org/x/net

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.

Specific Go Packages Affected

golang.org/x/net/http2/h2c

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/net`	≥ 0.0.0-20220524220425-1d687d428aca&&< 0.1.1-0.20221104162952-702349b0e862	0.1.1-0.20221104162952-702349b0e862

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update golang.org/x/net to 0.1.1-0.20221104162952-702349b0e862 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxg5-wq6x-vr4w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fxg5-wq6x-vr4w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fxg5-wq6x-vr4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests. ### Specific Go Packages Affected golang.org/x/net/http2/h2c

O3 Security · Impact-Aware SCA

Is GHSA-fxg5-wq6x-vr4w in your dependencies?

O3 detects GHSA-fxg5-wq6x-vr4w across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-fxg5-wq6x-vr4w