CVE-2026-71190

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (57th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-53048 (ENISA EUVD) · GHSA-4jj7-q8c5-78g4 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
57th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

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
Web page

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
Web page

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 9× in last 7d / 51× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 250 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-71190?
CVE-2026-71190 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-71190 published?
The CVE record for CVE-2026-71190 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
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 (57th 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?
A fix for CVE-2026-71190 is available: update to the fixed version the vendor names in its advisory. 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.