{"answers":{"affected":"3 open source packages ship an affected version, including Traefik and github.com/traefik/traefik. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-88010 in the wild and no public exploit code.","fix":"Upgrade Traefik to 3.7.13 or later.","what":"CVE-2026-88010 is a medium-severity vulnerability in Traefik Traefik, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-88010 and fix it if it is affected.\n\nWhat it is: CVE-2026-88010 is a medium-severity vulnerability in Traefik Traefik, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-88010 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Traefik (Go): affected from 3.6.11; fixed in 3.7.13\n- Traefik (Go): affected from 3.6.11; fixed in 3.7.13\n- github.com/traefik/traefik (Go): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-88010/ (Markdown: https://insights.sbomify.com/CVE-2026-88010/index.md)","id":"CVE-2026-88010","markdown":"https://insights.sbomify.com/CVE-2026-88010/index.md","name":"CVE-2026-88010","record":{"aliases":["GHSA-8fcf-v89g-xpg6","GO-2026-6558","MINI-c7x8-8cwp-h837","MINI-pw97-66qj-pmq6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"HTTP reverse proxy","requires_auth":"none","summary":"An attacker can enumerate valid usernames in Traefik BasicAuth configurations by exploiting timing differences caused by singleflight coalescing.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"traefik","vendor":"traefik"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Traefik is an open source HTTP reverse proxy and load balancer. From 3.6.11 until 3.7.13, checkPassword in pkg/middlewares/auth/basic_auth.go constructs the BasicAuth singleflight key from the submitted password and stored secret. Concurrent requests for absent usernames therefore coalesce on one key while configured usernames perform separate password hashes, creating an unauthenticated timing discrepancy that reveals whether a username exists. Sequential checks remain cost-equalized, Traefik v2 and Digest authentication are not affected, and the issue does not disclose credentials or bypass authentication. This issue is fixed in version 3.7.13.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Traefik: BasicAuth singleflight coalescing reintroduces an unauthenticated username-enumeration timing oracle","id":"CVE-2026-88010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":"traefik:traefik","products":["traefik:traefik"],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Traefik: ForwardAuth identity spoofing via dot-form header alias","id":"CVE-2026-88011"},"packages":[{"ecosystem":"Go","fixed":["3.7.13"],"introduced":["3.6.11"],"last_affected":[],"package":"Traefik","purl":null,"source":"GHSA-8fcf-v89g-xpg6"},{"ecosystem":"Go","fixed":["3.7.13"],"introduced":["3.6.11"],"last_affected":[],"package":"Traefik","purl":"pkg:golang/Traefik","source":"GHSA-8fcf-v89g-xpg6"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/traefik/traefik","purl":"pkg:golang/github.com/traefik/traefik","source":"GO-2026-6558"}],"prev":{"headline":"Traefik: Rootless HTTP/1 request-target routes as \"/\" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging","id":"CVE-2026-88009"},"products":["traefik"],"published":"2026-09-22","related":[{"cvss_score":9.8,"headline":"HTTP client can remove the X-Forwarded headers in Traefik","id":"CVE-2024-45410","kev_date_added":null,"published":"2024-09-19"},{"cvss_score":9.3,"headline":"Traefik v3.7.0 Authentication Bypass via from-to-www-redirect","id":"CVE-2026-88877","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.3,"headline":"Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth","id":"CVE-2026-85595","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":9.1,"headline":"Traefik HTTP/3 Backend NTLM Connection Reuse","id":"CVE-2026-88007","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.8,"headline":"Traefik: Rootless HTTP/1 request-target routes as \"/\" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging","id":"CVE-2026-88009","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.8,"headline":"Traefik has a possible vulnerability with the path matchers","id":"CVE-2025-32431","kev_date_added":null,"published":"2025-04-21"},{"cvss_score":8.2,"headline":"Traefik v3.7 Authentication Bypass via TLS Option Conflict","id":"CVE-2026-85596","kev_date_added":null,"published":"2026-09-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["traefik"]},"summary":"An attacker can enumerate valid usernames in Traefik BasicAuth configurations by exploiting timing differences caused by singleflight coalescing.","url":"https://insights.sbomify.com/CVE-2026-88010/"}