Traefik Inverted TLS Verification Logic in ingress-nginx Provider
CVE-2025-66491GHSA-7vww-mvcr-x6vj
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/traefik/traefik/v3 3.6.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/traefik/traefik/v3
- Affected
- >= 3.5.0, <= 3.6.2
- Fixed in
- 3.6.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7vww-mvcr-x6vj lists affected ranges: Go github.com/traefik/traefik/v3 >=3.5.0 <=3.6.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2025-66491: 0.22% estimated exploitation activity in the next 30 days; percentile 12.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact There is a potential vulnerability in Traefik NGINX provider managing the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation. The provider inverts the semantics of the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation. Setting the annotation to "on" (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected. Patches - https://github.com/traefik/traefik/releases/tag/v3.6.3 For more information If you have any questions or comments about this advisory, please open an issue. <details <summaryOriginal Description</summary Summary A logic error in Traefik's experimental ingress-nginx provider inverts the semantics of the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation. Setting the annotation to "on" (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-7vww-mvcr-x6vj
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-66491 Advisory: Traefik Inverted TLS Verification Logic in ingress-nginx Provider IDs: CVE-2025-66491, GHSA-7vww-mvcr-x6vj Record: https://patchnext.com/advisories/cve-2025-66491 (revision 1, source checked 26 Oct 2026, 15:13 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/traefik/traefik/v3 3.6.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/traefik/traefik/v3: affected >= 3.5.0, <= 3.6.2; fixed in 3.6.3 ## Suggested inspection (read-only) - Go github.com/traefik/traefik/v3: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/traefik/traefik/v3. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-7vww-mvcr-x6vj (GitHub-reviewed advisory GHSA-7vww-mvcr-x6vj lists affected ranges: Go github.com/traefik/traefik/v3 >=3.5.0 <=3.6.2) Commands are suggestions: review each one before running it.
Loading voting…