What is GHSA-7F4J-64P6-5H5V?

GHSA-7F4J-64P6-5H5V is a medium-severity security vulnerability in github.com/traefik/traefik/v2 (go), affecting versions < 2.11.2. It is fixed in 2.11.2, 3.0.0-rc5.

Which packages are affected by GHSA-7F4J-64P6-5H5V?

github.com/traefik/traefik/v2 (go) versions = 3.0.0-rc1, < 3.0.0-rc5.

Is there a fix for GHSA-7F4J-64P6-5H5V?

Yes. GHSA-7F4J-64P6-5H5V is fixed in 2.11.2, 3.0.0-rc5. Upgrade to this version or later.

Is GHSA-7F4J-64P6-5H5V exploitable, and should I be worried?

Whether GHSA-7F4J-64P6-5H5V 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-7F4J-64P6-5H5V 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-7F4J-64P6-5H5V?

Upgrade: github.com/traefik/traefik/v2 to 2.11.2 or later, github.com/traefik/traefik/v3 to 3.0.0-rc5 or later.

GHSA-7F4J-64P6-5H5V in github.com/traefik/traefik/v2 | Intelligent Application Security

Q: Which packages are affected by GHSA-7F4J-64P6-5H5V?

github.com/traefik/traefik/v2 (go) versions = 3.0.0-rc1, < 3.0.0-rc5.

Q: Is there a fix for GHSA-7F4J-64P6-5H5V?

Yes. GHSA-7F4J-64P6-5H5V is fixed in 2.11.2, 3.0.0-rc5. Upgrade to this version or later.

Q: Is GHSA-7F4J-64P6-5H5V exploitable, and should I be worried?

Whether GHSA-7F4J-64P6-5H5V 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-7F4J-64P6-5H5V 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-7F4J-64P6-5H5V?

Upgrade: github.com/traefik/traefik/v2 to 2.11.2 or later, github.com/traefik/traefik/v3 to 3.0.0-rc5 or later.

Summary

There is a potential vulnerability in Traefik managing HTTP/2 connections.

More details in the CVE-2023-45288.

Workarounds

No workaround

For more information

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

Impact

Affected versions

github.com/traefik/traefik/v2 (< 2.11.2) github.com/traefik/traefik/v3 (>= 3.0.0-rc1, < 3.0.0-rc5)

Security releases

github.com/traefik/traefik/v2 → 2.11.2 (go) github.com/traefik/traefik/v3 → 3.0.0-rc5 (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.

See it in your environment

Remediation advice

Frequently Asked Questions

What is GHSA-7F4J-64P6-5H5V? GHSA-7F4J-64P6-5H5V is a medium-severity security vulnerability in github.com/traefik/traefik/v2 (go), affecting versions < 2.11.2. It is fixed in 2.11.2, 3.0.0-rc5.
Which packages are affected by GHSA-7F4J-64P6-5H5V?
- github.com/traefik/traefik/v2 (go) (versions < 2.11.2)
- github.com/traefik/traefik/v3 (go) (versions >= 3.0.0-rc1, < 3.0.0-rc5)
Is there a fix for GHSA-7F4J-64P6-5H5V? Yes. GHSA-7F4J-64P6-5H5V is fixed in 2.11.2, 3.0.0-rc5. Upgrade to this version or later.
Is GHSA-7F4J-64P6-5H5V exploitable, and should I be worried? Whether GHSA-7F4J-64P6-5H5V 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-7F4J-64P6-5H5V 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-7F4J-64P6-5H5V?
- Upgrade github.com/traefik/traefik/v2 to 2.11.2 or later
- Upgrade github.com/traefik/traefik/v3 to 3.0.0-rc5 or later

Other vulnerabilities in github.com/traefik/traefik/v2

CVE-IDSeverityPackage summary

CVE-2026-54761Mediumgithub.com/traefik/traefik/v3: Traefik: Kubernetes Gateway crossProviderNamespaces bypass allows HTTPRoute outside the allowlist…CVE-2026-53622HighTraefik: Traefik: HTTP/3 mTLS bypass via exact SNI TLSOptions lookup for wildcard and mixed-case hosts CVE-2026-48020Highgithub.com/traefik/traefik/v2: Traefik has a StripPrefix Route-Level Auth Bypass via Path Normalization CVE-2026-44774Mediumgithub.com/traefik/traefik/v3: Traefik: Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure…CVE-2026-41181Mediumgithub.com/traefik/traefik/v2: Traefik's errors middleware forwards Authorization and Cookie headers to separate error page service