How severe is GHSA-4hjq-9h5c-252j?

No CVSS score has been assigned to GHSA-4hjq-9h5c-252j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4hjq-9h5c-252j?

GHSA-4hjq-9h5c-252j affects the following packages: github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-4hjq-9h5c-252j?

Update github.com/traefik/traefik/v2 to 2.11.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4hjq-9h5c-252j is resolved across your whole dependency graph.

How do I detect GHSA-4hjq-9h5c-252j 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4hjq-9h5c-252j 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-4hjq-9h5c-252j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4hjq-9h5c-252j can be triaged on real exposure rather than presence alone.

Is GHSA-4hjq-9h5c-252j actively exploited in the wild?

No public exploit code has been indexed for GHSA-4hjq-9h5c-252j 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-4hjq-9h5c-252j published, and has it been updated?

GHSA-4hjq-9h5c-252j was published on March 12, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-4hjq-9h5c-252j — v2

GHSA-4hjq-9h5c-252j is a security vulnerability in github.com/traefik/traefik/v2. A fix is available for github.com/traefik/traefik/v2 — see the affected versions and patch details below.

Traefik: HTTP/2 frames can cause a running server to panic

Also known asGO-2026-4684

Published

Mar 12, 2026

Updated

Mar 23, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Mar 23, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/traefik/traefik/v2🐹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

More Details:

Patches

For more information

If you have any questions or comments about this advisory, please open an issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/traefik/traefik/v2`	all versions	2.11.40`go get github.com/traefik/traefik/v2@v2.11.40`
🐹Go	`github.com/traefik/traefik/v3`	all versions	3.6.10`go get github.com/traefik/traefik/v3@v3.6.10`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/traefik/traefik/v2 to 2.11.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4hjq-9h5c-252j 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4hjq-9h5c-252j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4hjq-9h5c-252j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary More Details: - https://nvd.nist.gov/vuln/detail/CVE-2026-27141 - https://pkg.go.dev/golang.org/x/net/http2?tab=versions ## Patches - https://github.com/traefik/traefik/releases/tag/v3.6.10 - https://github.com/traefik/traefik/releases/tag/v2.11.40 ## For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

O3 Security · Impact-Aware SCA

Is GHSA-4hjq-9h5c-252j in your dependencies?

O3 Security finds GHSA-4hjq-9h5c-252j across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works