ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-fh26-gfpp-7xxx

snicheck skips the check when is nil (HTTP/2 )

Published Oct 7, 2026 · catalog updated Oct 7, 2026 · snicheck skips the check

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-fh26-gfpp-7xxx. A missing EPSS score is not a low risk. Compare snicheck skips the check with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (snicheck skips the check).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
go github.com/traefik/traefik/v2 · go github.com/traefik/traefik/v3

## Summary There is a high severity vulnerability in Traefik's SNI check, which makes sure a request received on a TLS connection is only served by an HTTP router whose TLS options match the ones negotiated for that connection. The check was skipped entirely when the request carried no TLS connection state. Traefik built with Go 1.27 leaves that state unset for HTTP/2 requests sent with the pseudo-header over a TLS connection, so an unauthenticated client could have such a request served by a router with different TLS options, for example one requiring a client certificate, without presenting one. Official Traefik binaries and images are built with Go 1.26 and are not exposed, but any Traefik build made with Go 1.27, including third-party rebuilds, is; Traefik now always sets the TLS state of requests received on a TLS connection, so the check applies whatever the toolchain. Traefik v3 versions below v3.7 are affected but are no longer maintained and will not receive a patch of their own; the remedy for those users is to upgrade to a maintained, patched version. ## Patches - https://github.com/traefik/traefik/releases/tag/v2.11.58 - https://github.com/traefik/traefik/releases/tag/v3.7.14 ## For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/traefik/traefik/v2<= v2.11.57
  • go github.com/traefik/traefik/v3>= v3.0.0, <= v3.7.13

How to fix GHSA-fh26-gfpp-7xxx

  • Upgrade

    GHSA-fh26-gfpp-7xxx lists a fix boundary at v2.11.57. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in <= v2.11.57 · 2 other packages on the advisory

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-fh26-gfpp-7xxx. A missing EPSS score is not a low risk. Compare snicheck skips the check with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with <= v2.11.57, >= v3.0.0, <= v3.7.13. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Traefik security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 7, 2026 · Maintainer security tabs

    Detected

    ## Summary There is a high severity vulnerability in Traefik's SNI check, which makes sure a request received on a TLS connection is only served by an HTTP router whose TLS options match the ones negotiated for that connection. The check was skipped entirely when the request carried no TLS connection state. Traefik built with Go 1.27 leaves that state unset for HTTP/2 requests sent with the pseudo

Sources

  • Maintainer security tabsVendor advisoryGHSA-fh26-gfpp-7xxx

    ## Summary There is a high severity vulnerability in Traefik's SNI check, which makes sure a request received on a TLS connection is only served by an HTTP router whose TLS options match the ones negotiated for that connection. The check was skipped entirely when the request carried no TLS connection state. Traefik built with Go 1.27 leaves that state unset for HTTP/2 requests sent with the pseudo

    github.com

Freshness

Last verified in this catalog Oct 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026