CVE Program Container

Answer in brief

CVE-2026-97149 records a Medium severity (CVSS 5.3) vulnerability in CVE Program Container. The current sources do not mark it as known exploited. The current feed maps OpenStack/Swift (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 24, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenStack/Swift (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenStack/Swiftgeneric	>=2.4.0 <2.35.5 \|\| >=2.36.0 <2.36.4 \|\| >=2.37.0 <2.37.4 \|\| >=2.38.0 <2.38.2	2.35.5, 2.36.4, 2.37.4, 2.38.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenStack/Swift.
Review the reported fix. Update OpenStack/Swift to 2.35.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 24, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.