cve.bz

CVE-2026-97149 openstack swift: Incomplete List of Disallowed Inputs

5.3 mediumEPSS 0.2%

Medium (5.3) in openstack swift. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In OpenStack Swift before 2.38.2, the tempurl middleware does not reject the X-Copy-From header on PUT requests. A TempURL signature only covers the method, expiry, and path, and thus the list of disallowed headers is the only defense against a signed PUT request changing what the request does. An attacker holding a PUT TempURL for a single object can add an X-Copy-From header naming any object in the same account; the copy middleware copies that object to the destination, and the attacker then reads the victim's data back with a GET TempURL for the destination object. Copies across account boundaries are rejected. Only deployments using the shipped default proxy pipeline (tempurl and copy middleware) with account-level TempURL keys are affected.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-184 Incomplete List of Disallowed Inputs
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-97149 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97149?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97149?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97149 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-97149

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-97149](https://cve.bz/cve/badge/CVE-2026-97149.svg)](https://cve.bz/cve/CVE-2026-97149)

HTML:

<a href="https://cve.bz/cve/CVE-2026-97149"><img src="https://cve.bz/cve/badge/CVE-2026-97149.svg" alt="CVE-2026-97149"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenStack Swiftfrom 2.4.0 before 2.35.5
OpenStack Swiftfrom 2.36.0 before 2.36.4
OpenStack Swiftfrom 2.37.0 before 2.37.4
OpenStack Swiftfrom 2.38.0 before 2.38.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12swift2.30.1-0+deb12u3DEBIAN-CVE-2026-97149
Debian13swift2.35.1-0+deb13u4DEBIAN-CVE-2026-97149
Debian14swift2.38.1-3DEBIAN-CVE-2026-97149
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moreswiftno fix listedUBUNTU-CVE-2026-97149

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate because a party who already holds a valid upload TempURL can read other objects in the same Swift account. The attack does not cross into another account, does not allow code execution, and requires the attacker to know the target container and object name. The tempurl middleware must be enabled. That middleware is part of the default Swift proxy pipeline.

The following Red Hat products ship openstack-swift builds that contain the vulnerable code and are affected: Red Hat OpenStack Platform 13 (openstack-swift 2.17.1), Red Hat OpenStack Platform 16.2 (openstack-swift 2.23.4), Red Hat OpenStack Platform 17.1 (openstack-swift 2.27.1), and Red Hat OpenStack Services on OpenShift 18 (openstack-swift 2.31.2).

Ansible Automation Platform and Red Hat Developer Hub are not affected. Name matches in those products are a JavaScript client library for Swift, not the Swift service.

Red Hat's mitigation

Until a product update is available, operators can drop the dangerous header in the proxy configuration. In the [filter:tempurl] section, add x-copy-from to the incoming_remove_headers option. Swift then removes the header, and the signed upload does not copy another object. This applies only where the tempurl middleware is enabled. If TempURL is not required, leaving that middleware out of the proxy pipeline also avoids the issue.

ProductPackageStateAdvisory
Red Hat OpenStack Platform 13 (Queens)openstack-swiftOut of support scope
Red Hat OpenStack Platform 16.2openstack-swiftAffected
Red Hat OpenStack Platform 17.1openstack-swiftAffected
Red Hat OpenStack Platform 18.0openstack-swiftAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97149.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
  • CAPEC-182 Flash Injection Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON