CVE-2026-71190

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.7Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In OpenStack Swift through 2.38.0, the proxy server Accept header parser contains a regular expression vulnerable to catastrophic backtracking (ReDoS). The "qdtext" pattern (?:[^"]|\\.)* allows an unauthenticated remote attacker to send a crafted Accept header that causes exponential CPU consumption in the proxy worker. A payload of 32 backslash-character pairs exceeds 30 seconds of CPU time. No authentication is required. Repeated requests can exhaust all proxy worker threads, resulting in a complete denial of service.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 5, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

OSSA-2026-031: Swift proxy denial of service via Accept header — OpenStack Security Advisories 0.0.1.dev359 documentation

https://security.openstack.org/ossa/OSSA-2026-031.html
generic

oss-security - [OSSA-2026-031] OpenStack Swift: Proxy denial of service via Accept header (CVE-2026-pending)

https://openwall.com/lists/oss-security/2026/07/28/27
generic

Bug #2158771 “[OSSA-2026-031] Unauthenticated remote DOS via mal...” : Bugs : OpenStack Object Storage (swift)

https://launchpad.net/bugs/2158771

Vendor Advisories for CVE-2026-71190(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
swift2.26.0-10 ... 2.37.1-6 (55 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
swift2.30.0-4, 2.30.1-0+deb12u1
  • every version up to 2.30.1-0+deb12u2: fixed in 2.30.1-0+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
swift2.35.0-4 ... 2.38.2-1 (26 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
swift2.35.0-4 ... 2.37.1-5 (17 versions)
  • every version up to 2.37.1-6: fixed in 2.37.1-6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 84× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 203 total refreshes for this CVE.

  1. 2026-10-04 23:37 UTCGHSA enrichment
  2. 2026-10-04 06:08 UTCEG score recompute
  3. 2026-10-04 06:08 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 01:14 UTCEG score recompute
  6. 2026-10-03 01:14 UTCGHSA enrichment
  7. 2026-10-02 17:56 UTCEPSS rescore
  8. 2026-10-02 10:03 UTCEG score recompute
  9. 2026-10-02 10:03 UTCGHSA enrichment
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-10-01 14:33 UTCGHSA enrichment
  12. 2026-10-01 02:23 UTCEG score recompute
  13. 2026-10-01 02:23 UTCGHSA enrichment
  14. 2026-09-30 15:03 UTCEPSS rescore
  15. 2026-09-29 06:23 UTCEG score recompute
  16. 2026-09-29 06:23 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 06:00 UTCGHSA enrichment
  19. 2026-09-27 17:52 UTCEG score recompute
  20. 2026-09-27 17:52 UTCGHSA enrichment
  21. 2026-09-27 13:48 UTCEPSS rescore
  22. 2026-09-26 15:59 UTCEPSS rescore
  23. 2026-09-25 04:38 UTCEG score recompute
  24. 2026-09-25 04:38 UTCGHSA enrichment
  25. 2026-09-24 04:24 UTCEG score recompute
Show 75 more
  1. 2026-09-24 04:24 UTCGHSA enrichment
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-23 16:13 UTCGHSA enrichment
  4. 2026-09-23 03:18 UTCEG score recompute
  5. 2026-09-23 03:18 UTCGHSA enrichment
  6. 2026-09-22 15:09 UTCGHSA enrichment
  7. 2026-09-22 02:31 UTCEG score recompute
  8. 2026-09-22 02:31 UTCGHSA enrichment
  9. 2026-09-21 21:09 UTCEPSS rescore
  10. 2026-09-20 20:50 UTCEG score recompute
  11. 2026-09-20 20:50 UTCGHSA enrichment
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-19 23:21 UTCEG score recompute
  14. 2026-09-19 23:21 UTCGHSA enrichment
  15. 2026-09-19 07:55 UTCEG score recompute
  16. 2026-09-19 07:55 UTCGHSA enrichment
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 17:45 UTCGHSA enrichment
  19. 2026-09-18 04:15 UTCEG score recompute
  20. 2026-09-18 04:15 UTCGHSA enrichment
  21. 2026-09-17 16:06 UTCGHSA enrichment
  22. 2026-09-17 01:09 UTCEG score recompute
  23. 2026-09-17 01:09 UTCGHSA enrichment
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
  26. 2026-09-16 05:15 UTCGHSA enrichment
  27. 2026-09-15 16:42 UTCEG score recompute
  28. 2026-09-15 16:42 UTCGHSA enrichment
  29. 2026-09-15 03:12 UTCEPSS rescore
  30. 2026-09-15 01:34 UTCGHSA enrichment
  31. 2026-09-14 07:39 UTCGHSA enrichment
  32. 2026-09-13 19:31 UTCEG score recompute
  33. 2026-09-13 19:31 UTCGHSA enrichment
  34. 2026-09-13 06:57 UTCGHSA enrichment
  35. 2026-09-12 18:35 UTCEG score recompute
  36. 2026-09-12 18:35 UTCGHSA enrichment
  37. 2026-09-12 15:02 UTCEPSS rescore
  38. 2026-09-12 06:26 UTCGHSA enrichment
  39. 2026-09-11 18:17 UTCEG score recompute
  40. 2026-09-11 18:17 UTCGHSA enrichment
  41. 2026-09-11 14:53 UTCEPSS rescore
  42. 2026-09-11 06:08 UTCGHSA enrichment
  43. 2026-09-10 17:57 UTCEG score recompute
  44. 2026-09-10 17:57 UTCGHSA enrichment
  45. 2026-09-10 09:35 UTCEPSS rescore
  46. 2026-09-10 04:26 UTCGHSA enrichment
  47. 2026-09-09 16:17 UTCGHSA enrichment
  48. 2026-09-09 06:31 UTCEG score recompute
  49. 2026-09-09 06:31 UTCGHSA enrichment
  50. 2026-09-08 22:01 UTCEPSS rescore
  51. 2026-09-08 08:14 UTCGHSA enrichment
  52. 2026-09-07 18:26 UTCEG score recompute
  53. 2026-09-07 18:26 UTCGHSA enrichment
  54. 2026-09-06 18:48 UTCEG score recompute
  55. 2026-09-06 18:48 UTCGHSA enrichment
  56. 2026-09-06 13:48 UTCEPSS rescore
  57. 2026-09-06 06:39 UTCGHSA enrichment
  58. 2026-09-05 18:30 UTCEG score recompute
  59. 2026-09-05 18:30 UTCGHSA enrichment
  60. 2026-09-05 04:00 UTCEG score recompute
  61. 2026-09-05 04:00 UTCGHSA enrichment
  62. 2026-09-04 10:01 UTCEG score recompute
  63. 2026-09-04 10:01 UTCGHSA enrichment
  64. 2026-09-04 05:07 UTCEPSS rescore
  65. 2026-09-03 20:36 UTCGHSA enrichment
  66. 2026-09-03 07:15 UTCEG score recompute
  67. 2026-09-03 07:14 UTCGHSA enrichment
  68. 2026-09-02 14:12 UTCEPSS rescore
  69. 2026-09-02 09:42 UTCGHSA enrichment
  70. 2026-09-01 20:46 UTCEG score recompute
  71. 2026-09-01 20:46 UTCGHSA enrichment
  72. 2026-09-01 13:54 UTCEPSS rescore
  73. 2026-09-01 04:40 UTCEPSS rescore
  74. 2026-08-31 22:56 UTCGHSA enrichment
  75. 2026-08-30 22:07 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-71190?
CVE-2026-71190 is a high vulnerability published on August 5, 2026. In OpenStack Swift through 2.38.0, the proxy server Accept header parser contains a regular expression vulnerable to catastrophic backtracking (ReDoS). The "qdtext" pattern (?:[^"]|\\.)* allows an unauthenticated remote attacker to send a crafted Accept header that causes exponential CPU…
When was CVE-2026-71190 disclosed?
CVE-2026-71190 was first published on August 5, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71190 actively exploited?
CVE-2026-71190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71190?
CVE-2026-71190 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71190?
No fix for CVE-2026-71190 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-71190 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71190

Explore →

Is Your Infrastructure Affected by CVE-2026-71190?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs