Vulnerability briefing · 2026-10-22 07:46 IST

CVE-2026-114636

Traefik v3.7.13 before v3.7.14 contains an access-control bypass in the Kubernetes Ingress NGINX provider, where the HTTP router generated for ssl-passthrough Ingresses on non-TLS entry points never applies the Ingress's access-control annotations. Unauthenticated attackers reaching the HTTP entry point with the Ingress host can access backends protected by auth-type, auth-url, or whitelist-source-range annotations, with nothing logged.

Executive briefing

This record describes a reported software or hardware weakness. The description and CVSS rating are source metadata; practical risk depends on whether your environment uses an affected product/version and whether the vulnerable component is reachable and configured in an exploitable way.

Assessment status: No CISA KEV listing is currently recorded in this local feed. This does not prove the vulnerability is not exploited.

Severity & exploitability

7.0 / 10 CVSS

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack vectorN
Attack complexityL
Privileges requiredN
User interactionN
ScopeX

Impacted products and platforms

Affected product configuration identifiers from NVD. Confirm exact versions and platform applicability against the vendor advisory.

Product / CPE identifierVersion rangeVulnerable match
cpe:2.3:a:traefik:traefik:3.7.13:*:*:*:*:*:*:*See vendor advisoryYes

How it works and what it could affect

The NVD description is the authoritative short summary currently available for this record. A detailed technical mechanism is not inferred when the source record does not provide one.

Weakness classification: CWE-306

Review the CVSS attack characteristics above to understand whether exploitation is network/local, whether privileges or user interaction are required, and which confidentiality, integrity or availability impacts are scored.

Remediation and recommended response

  1. Identify exposure: compare the affected product and version ranges below with your asset inventory, software bill of materials, endpoint inventory and externally exposed services.
  2. Remediate: review the linked vendor security advisory or patch notes, upgrade to a fixed release, or apply the vendor-provided workaround if an upgrade cannot be completed.
  3. Mitigate while patching: restrict network access to the vulnerable service, disable the affected feature where operationally safe, and monitor vendor/CERT advisories for updated guidance.
  4. Validate: confirm the fixed version or mitigation on representative systems, run a vulnerability rescan, and retain change evidence.

Vendor remediation / security advisories

Exploit intelligence & references

No CISA KEV match is recorded in the latest successful catalog refresh. This is not a guarantee that public proof-of-concept code or exploitation does not exist.

Sources: NVD and CISA KEV when available. Vendor confirmation remains the final authority for fixed versions and workarounds.

Open NVD record ← Back to CVE Watch