https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:42:53 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-348480 EUVD-2026-348480 https://cve.radiocsirt.org/vuln/euvd-2026-348480 https://cve.radiocsirt.org/vuln/fkie_cve-2026-71192 <p>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&#39;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&#39;s ACLs or ownership. This requires the non-default s3_acl=true configuration.</p> <p>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&#39;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&#39;s ACLs or ownership. This requires the non-default s3_acl=true configuration.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-71192 https://cve.radiocsirt.org/vuln/ghsa-6p2v-36c6-f6m5 <p>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&#39;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&#39;s ACLs or ownership. This requires the non-default s3_acl=true configuration.</p> <p>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&#39;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&#39;s ACLs or ownership. This requires the non-default s3_acl=true configuration.</p> https://cve.radiocsirt.org/vuln/ghsa-6p2v-36c6-f6m5 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-71192 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: swift, Ubuntu:18.04:LTS: swift, Ubuntu:20.04:LTS: swift, Ubuntu:22.04:LTS: swift, Ubuntu:24.04:LTS: swift, Ubuntu:26.04:LTS: swift</p> <p>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&#39;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&#39;s ACLs or ownership. This requires the non-default s3_acl=true configuration.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: swift, Ubuntu:18.04:LTS: swift, Ubuntu:20.04:LTS: swift, Ubuntu:22.04:LTS: swift, Ubuntu:24.04:LTS: swift, Ubuntu:26.04:LTS: swift</p> <p>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&#39;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&#39;s ACLs or ownership. This requires the non-default s3_acl=true configuration.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-71192