CVE-2026-71192: OpenStack Swift · Incorrect Authorization
Affects OpenStack SwiftSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 2.37.3 : update OpenStack Swift when convenient.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.37.3, 2.36.3, 2.35.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade OpenStack Swift to 2.37.3, 2.36.3 or 2.35.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenStackSwift | Affected
| Fixed in
|
AI-suggested
The vendor manages remediation for this cloud-hosted service. A patch is available for affected versions. Users should ensure they upgrade to a fixed version or apply the vendor's official fix. Since this vulnerability requires the non-default s3_acl=true configuration, disabling this setting can also mitigate the risk if patching is not immediately possible.
Description
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.