GHSA-m697-4v8f-55qg is a medium-severity (CVSS 4.8) CWE-913 vulnerability in github.com/traefik/traefik/v2. O3 Security confirms whether GHSA-m697-4v8f-55qg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Header dropping in traefik
Real-World Exposure
github.com/traefik/traefik/v2🐹github.com/traefik/traefikReal-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
Impact
There exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.
Details
If you have a chain of Traefik middlewares, and one of them sets a request header Important-Security-Header, then sending a request with the following Connection header will cause it to be removed before the request was sent:
curl 'https://example.com' -H "Connection: Important-Security-Header" -0
In this case, the backend does not see the request header Important-Security-Header.
Patches
Traefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13
Workarounds
No.
For more information
If you have any questions or comments about this advisory, open an issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/traefik/traefik/v2 | all versions | 2.4.13 |
| 🐹Go | github.com/traefik/traefik | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
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.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m697-4v8f-55qg 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-m697-4v8f-55qg 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-m697-4v8f-55qg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m697-4v8f-55qg in your dependencies?
O3 detects GHSA-m697-4v8f-55qg across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.