CVE-2026-85595
A public proof of concept exists; no exploitation attested.
- Published2026-09-04
- Fixed in3.7.11 · 2.11.55
- WeaknessCWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Traefik versions before v2.11.55 and versions v3.0.0 through v3.7.10 contain an authentication bypass vulnerability in the digestAuth middleware where unknown usernames receive an empty secret instead of rejection. Attackers can compute a valid digest response using the empty secret and arbitrary credentials to bypass authentication on any digestAuth-protected route without a valid username or password.
Timeline
dates in UTC- 2026-09-0412:17CVE publishedNVD
- 2026-10-2523:12First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-29 15:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-85595?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-85595?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.x | ≥ 3.0.0, < 3.7.11 | 3.7.11 | NVD |
| 2.11 | < 2.11.55 | 2.11.55 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
github.com/traefik/traefik: Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth
devspaces/traefik-rhel9 as a component of Red Hat OpenShift Dev Spaces
Fix
- Update Traefik to 3.7.11 · 2.11.55
- Workaround from the vendor Red Hat Product Security CVE-2026-85595 · 1 productDisable the digestAuth middleware and transition to alternative authentication mechanisms such as basicAuth, ForwardAuth, or mTLS. Alternatively, restrict network access to digestAuth-protected routes at an upstream gateway or network firewall until patched.
- No fix available, says the vendor Red Hat Product Security CVE-2026-85595 · 1 productAffected
Advisories and patches
- github.comMitigation · Patch · Vendor Advisory
Detection
read 2026-10-29 05:04 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- CISA-ADPSSVC decisionnone2026-09-04
- OpenCVESSVC decisionnone—
- CNACVSS 4.09.3read 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-287read 2026-10-23
- FIRST EPSSEPSS score2.5 %2026-10-29
- PoC-in-GitHubproof of concept1read 2026-10-29
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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
- Published
- 2026-09-04
- Last Modified
- 2026-10-08
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-85595?
Is CVE-2026-85595 actively exploited?
What is the CVSS score for CVE-2026-85595?
Running github.com/traefik/traefik? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.