withdrawn 2026-10-22 03:24Z

This entry duplicated another and was withdrawn in its favour.

Superseded by ETK-2026-2379.

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

withdrawn
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 <= v2.11.57; >= v3.0.0, <= v3.7.13
fixed in v2.11.58, v3.7.14
ETK-2026-1235Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/Traefik
8h 34msince last run
–AI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Traefik builds made with Go 1.27 can fail to enforce the TLS options associated with a routed request. An unauthenticated client may reach a route configured with different TLS requirements, potentially including client-certificate authentication, when using an affected HTTP/2 request over TLS. Official binaries and images built with Go 1.26 are not affected.

mitigation

Upgrade Traefik to v2.11.58 or v3.7.14. Replace any Go 1.27-built deployment with a patched release built using the corrected code path.

fixed in v2.11.58, 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.
–
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
–
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

No signals recorded for this entry yet.

this entry in the feed

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

{
  "etk_id": "ETK-2026-1235",
  "cve_id": null,
  "display_id": "ETK-2026-1235",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "retired",
  "anchor_state": "awaiting_cve",
  "title": "TLS option enforcement bypass in Traefik",
  "summary": "Traefik builds made with Go 1.27 can fail to enforce the TLS options associated with a routed request. An unauthenticated client may reach a route configured with different TLS requirements, potentially including client-certificate authentication, when using an affected HTTP/2 request over TLS. Official binaries and images built with Go 1.26 are not affected.",
  "mitigation": "Upgrade Traefik to v2.11.58 or v3.7.14. Replace any Go 1.27-built deployment with a patched release built using the corrected code path.",
  "vendor": "go",
  "product": "traefik",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= v2.11.57"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v2.11.58"
      ],
      "package_name": "Traefik",
      "purl": "pkg:golang/Traefik"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= v3.0.0, <= v3.7.13"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v3.7.14"
      ],
      "package_name": "Traefik",
      "purl": "pkg:golang/Traefik"
    }
  ],
  "cwes": null,
  "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {}
}

published 2026-10-11 10:35Z
last change 2026-10-22 03:24Z

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.