CVE Intelligence
High

CVE-2026-114656 — Traefik before 2.11.58 and 3.7.13 mTLS Bypass via Negated Host Matcher

Traefik before 2.11.58 and 3.7.13 contains an authentication bypass vulnerability that allows unauthenticated clients to skip client-certificate checks because negated Host matchers are counted as served domains. Attackers can reach backends protected by RequireAndVerifyClientCert when a router rule with !Host() creates a TLS options conflict that falls back to the default options.

Published Oct 21, 2026 · Updated Oct 22, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.16%
ahead of 5% of scored CVEs · Oct 27, 2026
Affects
Traefik
Traefik
CVSS base
7.5
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Traefik Traefik).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Traefik Traefik < 2.11.58≥ 3.0.0 and < 3.7.13 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 4.0 Medium — — disclosure@vulncheck.com via NIST National Vulnerability Database
6.9 CVSS 4.0 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
7.5 CVSS 3.1 High 2.2 4.7 disclosure@vulncheck.com via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-436

Other CVEs with this weakness →

EPSS over time FIRST

Oct 22, 2026 → Oct 27, 2026 · 6 reading(s) · max 0.16%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Undergoing Analysis
    Oct 22, 2026 · NIST National Vulnerability Database
  • Affected products added · traefik/traefik
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • CVSS changed · 7.5
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • CVE published
    Oct 21, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 21, 2026 – Oct 21, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

2 on the record

Elsewhere on this site

Traefik
every CVE for this vendor
CWE-436
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114642 Traefik before 2.11.58 and 3.7.14 TLS Config Bypass via NTLM/Kerberos Round Tripper 6d
  • CVE-2026-114641 Traefik before 2.11.58 and 3.7.14 Race Condition in NTLM/Kerberos Round Tripper 6d
  • CVE-2026-114639 Traefik before 2.11.58 and 3.7.14 Authentication Bypass via Negotiate Connection Pool 6d
  • CVE-2026-114637 Traefik v3.2.0 before v3.7.14 FastProxy NTLM/Negotiate Connection Pool Identity Leak 6d
  • CVE-2026-114638 Traefik v3.7.0 before v3.7.14 Client CA Mix-up via auth-tls-secret Name Collision 6d
  • CVE-2026-114636 Traefik v3.7.13 Authentication Bypass via ssl-passthrough Ingress HTTP Router 6d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-114656 is "Traefik before 2.11.58 and 3.7.13 mTLS Bypass via Negated Host Matcher", rated High. It affects Traefik (Traefik); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.16% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.