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

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

GHSA-qvj7-gq9c-hp7q ↗

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.13, <= v3.7.13
fixed in v3.7.14
CWE-306 Missing Authentication for Critical Function
ETK-2026-972, no cve assigned
pkg:golang/Traefik
13d 08h 47msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+0.5d
+5d
+10d
+15d

description

Traefik v3.7.13 can expose backends from SSL-passthrough Kubernetes Ingress resources through an HTTP route without applying configured authentication or source restrictions. An unauthenticated client may reach an affected backend if it can access the relevant HTTP entry point and target the Ingress host.

mitigation

Upgrade Traefik to v3.7.14. Until the upgrade is complete, restrict access to affected HTTP entry points or remove SSL passthrough from affected Ingress resources.

fixed in v3.7.14

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
10m
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-07 08:47Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-972",
  "cve_id": null,
  "display_id": "ETK-2026-972",
  "ghsa_id": "GHSA-qvj7-gq9c-hp7q",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Access-control bypass in Traefik Kubernetes Ingress NGINX provider",
  "summary": "Traefik v3.7.13 can expose backends from SSL-passthrough Kubernetes Ingress resources through an HTTP route without applying configured authentication or source restrictions. An unauthenticated client may reach an affected backend if it can access the relevant HTTP entry point and target the Ingress host.",
  "mitigation": "Upgrade Traefik to v3.7.14. Until the upgrade is complete, restrict access to affected HTTP entry points or remove SSL passthrough from affected Ingress resources.",
  "vendor": "go",
  "product": "go:Traefik",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= v3.7.13, <= v3.7.13"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v3.7.14"
      ],
      "package_name": "Traefik",
      "purl": "pkg:golang/Traefik"
    }
  ],
  "cwes": [
    306
  ],
  "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": 9.623294033333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T08:47:51+00:00",
      "days": -13.874698974270833,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:25.014083+00:00",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-qvj7-gq9c-hp7q"
    }
  }
}

published 2026-10-08 13:38Z
last change 2026-10-21 05:31Z

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.