EUVD-2026-53049
GHSA-hqwm-h3rj-hvcf
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Presigned URL IS the server-side credential so PR:N; AC:L once URL is held; C:H only, no integrity or availability impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
OpenStack Swift's S3API middleware through version 2.38.0 fails to enforce SigV4 signature coverage over semantic x-amz-* headers on presigned URL requests, enabling unauthorized server-side object copy operations under the signer's authorization context. An attacker holding a valid presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, redirecting Swift's behavior from a client upload into a server-side copy that reads any object accessible to the URL's original signer - effectively allowing privilege escalation within a delegated authorization context. No public exploit or CISA KEV listing was identified at time of analysis, but all deployments running the S3API middleware under the default s3_acl=false configuration are affected.
Technical ContextAI
OpenStack Swift (CPE: cpe:2.3:a:openstack:swift:*:*:*:*:*:*:*:*) is an open-source distributed object storage system that optionally exposes an Amazon S3-compatible API through its S3API middleware component. AWS Signature Version 4 (SigV4) authenticates S3 API requests by requiring that a defined set of headers be enumerated in a SignedHeaders field and their values hashed into a canonical request string; presigned URLs embed this computed signature in the URL itself, allowing time-limited delegated access to a single operation without exposing the signer's credentials directly. The critical design contract is that any header influencing request semantics must be included in the signed envelope - otherwise the signature provides no tamper protection for those headers. CWE-863 (Incorrect Authorization) identifies the root cause: Swift's S3API layer evaluates and honors the X-Amz-Copy-Source header even when it was not part of the signed request, meaning the authorization check validates the identity of the signer but not the scope of what the signer authorized. The X-Amz-Copy-Source header is a semantic directive that transforms a PUT operation into a server-side S3 Copy, causing Swift to fetch and copy from the named source object using the signer's existing access tokens rather than accepting a client-supplied upload body.
RemediationAI
Apply the patch described in OpenStack Security Advisory OSSA-2026-030 (https://security.openstack.org/ossa/OSSA-2026-030.html); an exact fixed release version number was not confirmed in the available intelligence data and must be obtained directly from the advisory before upgrading. As an immediate compensating control, operators should audit and restrict which application workflows are authorized to issue presigned PUT URLs, minimizing the population of parties who could exploit this flaw; trade-off is operational friction for upload workflows. If the S3API middleware is not required for current workloads, disabling it entirely eliminates the attack surface with no impact to consumers of the native Swift API, though this breaks S3-compatible client integrations. Enabling s3_acl=true changes bucket ACL enforcement behavior but does not patch the unsigned header acceptance flaw and introduces additional configuration management complexity. Operators should also add monitoring for X-Amz-Copy-Source headers appearing on PUT requests in Swift access logs as a detection signal for exploitation attempts in the interim period before patching.
Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.2
Eval injection vulnerability in the create method in the Bookmarks controller in Foreman before 1.2.0-RC2 allows remote
The create method in app/controllers/users_controller.rb in Foreman before 1.2.0-RC2 allows remote authenticated users w
Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addres
The Floppy Disk Controller (FDC) in QEMU, as used in Xen 4.5.x and earlier and KVM, allows local guest users to cause a
Memory Corruption was discovered in the cmsgpack library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10,
The IPTables firewall in OpenStack Neutron before 7.0.4 and 8.0.0 through 8.1.0 allows remote attackers to bypass an int
An issue in OpenStack magnum yoga-eom version allows a remote attacker to execute arbitrary code via the cert_manager.py
An Integer Overflow issue was discovered in the struct library in the Lua subsystem in Redis before 3.2.12, 4.x before 4
glibc contains a vulnerability that allows specially crafted LD_LIBRARY_PATH values to manipulate the heap/stack, causin
Buffer overflow in the pcnet_receive function in hw/net/pcnet.c in QEMU, when a guest NIC has a larger MTU, allows remot
Code injection in OpenStack Vitrage query parser allows authenticated users to execute arbitrary Python code through cra
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today