Incorrect Authorization Affecting openstack-swift-container package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.25% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-OPENSTACKSWIFTCONTAINER-18573605
  • published7 Aug 2026
  • disclosed28 Jul 2026

Introduced: 28 Jul 2026

NewCVE-2026-71192  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 openstack-swift-container.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openstack-swift-container package and not the openstack-swift-container package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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 Base Scores

version 3.1