# CVE-2026-131920: In OpenStack Cinder before 29.1.1, by making an os-initialize_connection request with an IQN that includes a path traversal as part of the c


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y/R:I/V:D/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-131920, GHSA-xrpq-2pv7-g346, UBUNTU-CVE-2026-131920

## What is CVE-2026-131920?

CVE-2026-131920 is a medium-severity vulnerability in OpenStack Cinder, published on 18 Nov 2026. 

### Official description

In OpenStack Cinder before 29.1.1, by making an os-initialize_connection request with an IQN that includes a path traversal as part of the connector's initiator element, an authenticated user with a 'member' role may create or overwrite files in the volume host filesystem. Only cinder-volume hosts using the LIO iSCSI target driver are affected. This target driver is typically used with the LVM volume driver.

Weakness: CWE-99 (Improper Control of Resource Identifiers)

## Which versions are affected by CVE-2026-131920?


## How do I fix CVE-2026-131920?

Upgrade OpenStack Cinder to 29.1.1 or later. The advisory says that version fixes it.

## Is CVE-2026-131920 being exploited?

There is no known exploitation of CVE-2026-131920 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131920 and fix it if it is affected.

What it is: CVE-2026-131920 is a medium-severity vulnerability in OpenStack Cinder, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131920 in the wild and no public exploit code.

Affected product: OpenStack Cinder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131920/ (Markdown: https://insights.sbomify.com/CVE-2026-131920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131920
- OSV: https://osv.dev/vulnerability/CVE-2026-131920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131920/
Summaries are generated and may contain mistakes; the official description above is the record.
