ETK-2026-1909Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-p8wx-ph99-xgcr ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
go:Traefik >= v3.7.0-ea.1, <= v3.7.14
fixed in v3.7.15
CWE-287 Improper Authentication
ETK-2026-1909Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/Traefik
2d 12h 53msince last run
1h 28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+2.7d
0
+1d
+2d
+3d
+4d
+5d

description

Traefik's Kubernetes Ingress NGINX provider can fail to enforce client-certificate authentication for a shared host when its Ingress resources use inconsistent mutual-TLS settings. A remote unauthenticated attacker may then access backends intended to require a client certificate, unless strict TLS options are enabled.

mitigation

Upgrade Traefik to v3.7.15. Until upgraded, enable core.strictTLSOptions and ensure Ingress resources sharing a host use consistent mutual-TLS configuration.

fixed in v3.7.15

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-16 08:00Z

this entry in the feed

GET /api/v1/feed/ETK-2026-1909

{
  "etk_id": "ETK-2026-1909",
  "cve_id": null,
  "display_id": "ETK-2026-1909",
  "ghsa_id": "GHSA-p8wx-ph99-xgcr",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Mutual TLS authentication bypass in Traefik Kubernetes Ingress",
  "summary": "Traefik's Kubernetes Ingress NGINX provider can fail to enforce client-certificate authentication for a shared host when its Ingress resources use inconsistent mutual-TLS settings. A remote unauthenticated attacker may then access backends intended to require a client certificate, unless strict TLS options are enabled.",
  "mitigation": "Upgrade Traefik to v3.7.15. Until upgraded, enable `core.strictTLSOptions` and ensure Ingress resources sharing a host use consistent mutual-TLS configuration.",
  "vendor": "go",
  "product": "go:Traefik",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= v3.7.0-ea.1, <= v3.7.14"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v3.7.15"
      ],
      "package_name": "Traefik",
      "purl": "pkg:golang/Traefik"
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 87.84203486666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T08:00:58+00:00",
      "days": -5.2332718328125,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T13:36:52.823246+00:00",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-p8wx-ph99-xgcr"
    }
  }
}

published 2026-10-17 21:43Z
last change 2026-10-21 13:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.