CVE-2026-71191

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. 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
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: None knownExposed: 0

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

In OpenStack Swift through 2.38.0, S3API middleware does not enforce that semantic x-amz-* headers are covered by the SigV4 signature on presigned URL requests. An attacker who obtains a presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, causing Swift to perform a server-side copy from an arbitrary source object using the signer's authorization context. The attacker can read any object the signer has access to, provided the target project_id, container name, and object name are known. This affects all deployments using the default s3_acl=false configuration.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

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
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 6, 2026

Advisory Details (3)

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

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
generic

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

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

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-71191(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 rangeFixed inDependents
swift2.26.0-10 ... 2.37.1-6 (55 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
swift2.30.0-4 ... 2.37.1-6 (42 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
swift2.35.0-4 ... 2.37.1-6 (20 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
swift2.35.0-4 ... 2.37.1-5 (17 versions)2.37.1-6

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 49× 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.

  1. 2026-08-20 10:13 UTCEG score recompute
  2. 2026-08-20 10:13 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 08:44 UTCEG score recompute
  5. 2026-08-19 08:44 UTCGHSA enrichment
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 07:14 UTCEG score recompute
  9. 2026-08-18 07:14 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 05:45 UTCEG score recompute
  12. 2026-08-17 05:45 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 03:50 UTCEG score recompute
  16. 2026-08-16 03:50 UTCGHSA enrichment
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 02:21 UTCEG score recompute
  19. 2026-08-15 02:21 UTCGHSA enrichment
  20. 2026-08-15 01:31 UTCEPSS rescore
  21. 2026-08-14 00:52 UTCEG score recompute
  22. 2026-08-14 00:52 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 23:23 UTCEG score recompute
  25. 2026-08-12 23:23 UTCGHSA enrichment
Show 24 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 21:54 UTCEG score recompute
  3. 2026-08-11 21:54 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 20:25 UTCGHSA enrichment
  6. 2026-08-09 18:56 UTCEG score recompute
  7. 2026-08-09 18:56 UTCGHSA enrichment
  8. 2026-08-09 13:47 UTCEPSS rescore
  9. 2026-08-08 17:27 UTCEG score recompute
  10. 2026-08-08 17:27 UTCGHSA enrichment
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 15:57 UTCGHSA enrichment
  13. 2026-08-06 14:28 UTCEG score recompute
  14. 2026-08-06 14:28 UTCGHSA enrichment
  15. 2026-08-06 13:54 UTCEG score recompute
  16. 2026-08-06 13:54 UTCGHSA enrichment
  17. 2026-08-06 13:47 UTCEPSS rescore
  18. 2026-08-06 07:51 UTCEG score recompute
  19. 2026-08-06 07:51 UTCGHSA enrichment
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-05 06:22 UTCEG score recompute
  23. 2026-08-05 05:34 UTCEG score recompute
  24. 2026-08-05 05:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71191?
CVE-2026-71191 is a medium vulnerability published on August 5, 2026. In OpenStack Swift through 2.38.0, S3API middleware does not enforce that semantic x-amz-* headers are covered by the SigV4 signature on presigned URL requests. An attacker who obtains a presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, causing Swift to perform a server-side copy…
When was CVE-2026-71191 disclosed?
CVE-2026-71191 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71191 actively exploited?
CVE-2026-71191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.1% of all scored CVEs.
What is the CVSS score of CVE-2026-71191?
CVE-2026-71191 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-71191?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71191, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-71191?

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