ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-qvj7-gq9c-hp7q

Kubernetes Ingress NGINX provider: ssl-passthrough sibling HTTP router serves the auth-protected backend without auth

Published Oct 7, 2026 · catalog updated Oct 7, 2026 · Kubernetes Ingress NGINX provider:

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-qvj7-gq9c-hp7q. A missing EPSS score is not a low risk. Compare Kubernetes Ingress NGINX provider: 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 (Kubernetes Ingress NGINX provider:).
  • 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/v3

## Summary There is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. Since v3.7.13, an Ingress carrying the annotation gets, besides its TCP passthrough router, an HTTP router on the non-TLS entry points that proxies to the backend. That router was built outside the regular per-rule processing, so the access-control annotations set on the same Ingress, such as with , and , were parsed but never turned into middlewares on it. An unauthenticated client reaching the HTTP entry point with the Ingress host could therefore reach a backend the operator had annotated as protected, with no authentication and no source allow-listing applied, and nothing logged. The HTTP side of an ssl-passthrough Ingress is now built like any other Ingress, with its annotation directives applied; the routers it generates are renamed as a result, see the v3.7.14 migration guide. Traefik v2 and Traefik v3 versions before v3.7.13 are not affected. ## Patches - 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/v3>= v3.7.13, <= v3.7.13

How to fix GHSA-qvj7-gq9c-hp7q

  • Upgrade

    GHSA-qvj7-gq9c-hp7q lists a fix boundary at v3.7.13. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in >= v3.7.13 · 1 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-qvj7-gq9c-hp7q. A missing EPSS score is not a low risk. Compare Kubernetes Ingress NGINX provider: with the linked advisory before you change production.

Which versions are affected?

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

What should an analyst verify?

CWE-306: Missing Authentication for Critical Function. 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

Kubernetes securityNginx securityTraefik 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 Kubernetes Ingress NGINX provider. Since v3.7.13, an Ingress carrying the annotation gets, besides its TCP passthrough router, an HTTP router on the non-TLS entry points that proxies to the backend. That router was built outside the regular per-rule processing, so the access-control annotations set on the same Ingress, such as with , a

Sources

  • Maintainer security tabsVendor advisoryGHSA-qvj7-gq9c-hp7q

    ## Summary There is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. Since v3.7.13, an Ingress carrying the annotation gets, besides its TCP passthrough router, an HTTP router on the non-TLS entry points that proxies to the backend. That router was built outside the regular per-rule processing, so the access-control annotations set on the same Ingress, such as with , a

    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