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


Severity

Recommended
0.0
high
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-18573705
  • published7 Aug 2026
  • disclosed28 Jul 2026

Introduced: 28 Jul 2026

NewCVE-2026-71191  (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, 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 Base Scores

version 3.1