How severe is GHSA-5423-jcjm-2gpv?

GHSA-5423-jcjm-2gpv has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5423-jcjm-2gpv?

GHSA-5423-jcjm-2gpv affects the following packages: github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go), github.com/traefik/traefik/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-5423-jcjm-2gpv?

Update github.com/traefik/traefik/v2 to 2.11.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5423-jcjm-2gpv is resolved across your whole dependency graph.

How do I detect GHSA-5423-jcjm-2gpv in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik/v2. 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-5423-jcjm-2gpv 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-5423-jcjm-2gpv?

O3 pinpoints whether GHSA-5423-jcjm-2gpv 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-5423-jcjm-2gpv actively exploited in the wild?

No public exploit code has been indexed for GHSA-5423-jcjm-2gpv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5423-jcjm-2gpv published, and has it been updated?

GHSA-5423-jcjm-2gpv was published on April 18, 2025 and was last updated on April 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-5423-jcjm-2gpv: v2 (Critical 9.1)

Blast Radius

3 pkgs affected

🐹github.com/traefik/traefik/v2🐹github.com/traefik/traefik/v3🐹github.com/traefik/traefik/v3

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

Summary

net/http: request smuggling through invalid chunked data: The net/http package accepts data in the chunked transfer encoding containing an invalid chunk-size line terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a bare LF in a chunk extension as part of the extension, this could permit request smuggling. [CVE-2025-22871] Vendor Affected Components: Go: 1.23.x < 1.23.8

More Details: CVE-2025-22871

Patches

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/traefik/traefik/v2`	all versions	2.11.24
🐹Go	`github.com/traefik/traefik/v3`	all versions	3.3.6
🐹Go	`github.com/traefik/traefik/v3`	≥ 3.4.0-rc1&&< 3.4.0-rc2	3.4.0-rc2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik/v2. 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 github.com/traefik/traefik/v2 to 2.11.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5423-jcjm-2gpv 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-5423-jcjm-2gpv 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-5423-jcjm-2gpv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary net/http: request smuggling through invalid chunked data: The net/http package accepts data in the chunked transfer encoding containing an invalid chunk-size line terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a bare LF in a chunk extension as part of the extension, this could permit request smuggling. [CVE-2025-22871] Vendor Affected Components: Go: 1.23.x < 1.23.8 More Details: [CVE-2025-22871](https://nvd.nist.gov/vuln/detail/CVE-2025-22871) ## Patches - https://github.com/traefik/traefik/releases/tag/v2.11.24 - https://g

O3 Security · Impact-Aware SCA

Is GHSA-5423-jcjm-2gpv in your dependencies?

O3 detects GHSA-5423-jcjm-2gpv 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-5423-jcjm-2gpv