CVE-2026-71192

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th 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

Also known asEUVD-2026-53050 (ENISA EUVD) · GHSA-6p2v-36c6-f6m5 (GitHub Security Advisories)Source: ENISA EUVD

6.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In OpenStack Swift through 2.38.0, the S3API middleware does not sanitize Swift-native control headers (X-Copy-From, X-Copy-From-Account) from S3 API requests when s3_acl=true. An attacker can inject these headers into a signed PUT request targeting their own bucket, causing Swift to perform a server-side copy from another tenant's private object. The source object authorization is bypassed because the S3API middleware has already authorized the request against the destination. The attacker can read any object whose project_id, container name, and object name are known, regardless of the source object's ACLs or ownership. This requires the non-default s3_acl=true configuration.

CVSS
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity60% × 45%
Impact severity (EG Severity): CVSS 6.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
38th
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 (6.0): severity, escalated by confirmed exploitation. This CVE's 6.0 is its impact severity (EG Severity), not escalated.

EG Severity
6.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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-030: Swift S3API header authorization bypass — OpenStack Security Advisories 0.0.1.dev359 documentation

https://security.openstack.org/ossa/OSSA-2026-030.html
Web page

oss-security - [OSSA-2026-030] OpenStack Swift: S3API header authorization bypass (CVE-2026-pending)

https://openwall.com/lists/oss-security/2026/07/28/26
Web page

Bug #2158733 “[OSSA-2026-030] Swift S3API header authorization b...” : Bugs : OpenStack Object Storage (swift)

https://launchpad.net/bugs/2158733

Vendor Advisories for CVE-2026-71192(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, 2.30.1-0+deb12u2
  • every version up to 2.30.1-0+deb12u3: fixed in 2.30.1-0+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
swift2.35.0-4, 2.35.1-0+deb13u1, 2.35.1-0+deb13u2
  • every version up to 2.35.1-0+deb13u3: fixed in 2.35.1-0+deb13u3
—
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 6× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 224 rows 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 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-71192?
CVE-2026-71192 is a medium-severity vulnerability; its CVE record was published on August 5, 2026. In OpenStack Swift through 2.38.0, the S3API middleware does not sanitize Swift-native control headers (X-Copy-From, X-Copy-From-Account) from S3 API requests when s3_acl=true. An attacker can inject these headers into a signed PUT request targeting their own bucket, causing Swift to perform a…
When was the CVE record for CVE-2026-71192 published?
The CVE record for CVE-2026-71192 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-71192 actively exploited?
CVE-2026-71192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71192?
CVE-2026-71192 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71192?
A fix for CVE-2026-71192 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71192 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-71192

Explore →

Is Your Infrastructure Affected by CVE-2026-71192?

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