Skip to main content
Menu
CVEs

Red Hat OpenStack Platform 13 command injection in Cinder storage driver SSH handling

CVE-2026-133189Published November 19, 2026, updated

9.6CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

The flaw is in the openstack-cinder package in Red Hat OpenStack Platform, where incomplete validation of shell metacharacters in Cinder's SSH-based storage-driver support lets an attacker with a low-privilege login reach it remotely over the network by supplying crafted connection information. Injected commands run with the privileges of Cinder's configured backend account, which can disclose storage configuration and, if that account has administrative rights, change storage used by other tenants and affect its integrity or availability.

Written by a model

Original description

A command injection vulnerability was found in OpenStack Cinder's SSH-based storage-driver support. Incomplete validation of shell metacharacters allows an authenticated user who owns a volume on an affected backend to supply crafted connection information and inject additional commands into the storage array's management interface. Commands execute with the privileges of Cinder's configured backend account. This can disclose storage configuration information and, where that account has administrative permissions, could allow changes that affect the integrity or availability of other tenants' storage.

What to do

  1. Check whether your setup matches what the bug needs.

    Cinder driver uses SSH to reach the storage array and calls the shared check_ssh_injection sanitizer (e.g. IBM Storwize/SVC) An SSH-based Cinder backend is actually configured (not present in a default devstack)
  2. Workaround: Avoiding or disabling the affected SSH-based backend removes this attack path

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133189 (Openstack-cinder: storwize: cinder: ssh command injection through incomplete metacharacter validation in storage drivers), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133189 (entry last updated 2026-11-19):
Affected:
- Red Hat Red Hat OpenStack Platform 13 (Queens): version range not reported
- Red Hat Red Hat OpenStack Platform 16.2: version range not reported
- Red Hat Red Hat OpenStack Platform 17.1: version range not reported
- Red Hat Red Hat OpenStack Platform 18.0: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Cinder driver uses SSH to reach the storage array and calls the shared check_ssh_injection sanitizer (e.g. IBM Storwize/SVC) (source: https://bugs.launchpad.net/cinder/+bug/2163356)
- An SSH-based Cinder backend is actually configured (not present in a default devstack) (source: https://bugs.launchpad.net/cinder/+bug/2163356)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Avoiding or disabling the affected SSH-based backend removes this attack path (source: https://www.cve.org/CVERecord?id=CVE-2026-133189)
CISA KEV: CVE-2026-133189 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133189 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2572315
- https://access.redhat.com/security/cve/CVE-2026-133189
- https://bugs.launchpad.net/cinder/+bug/2163356
- https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GVGTCVPAK7FUP72SYT2Y3RHNX4JDFU4N/
- https://review.opendev.org/c/openstack/cinder/+/1014986
- https://www.cve.org/CVERecord?id=CVE-2026-133189
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133189
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133189"}.

Affected versions

cve.now Index

48Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Shipped in major Linux distributions
  • Severity9.6/10CVSS 9.6
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 83 if added to CISA KEV
  • Would score about 78 if CISA's SSVC rates exploitation active
  • Would score about 55 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  5. Record last updated

Evidence 7

Questions about CVE-2026-133189

Is CVE-2026-133189 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The bug is an SSH command injection in Cinder storage drivers. The shared check_ssh_injection sanitizer does not validate all shell metacharacters, so crafted input can alter the commands sent over SSH to the storage array.

Source: bugs.launchpad.net, cve.org

Am I affected, and how do I check?

The advisory lists Red Hat OpenStack Platform 13 (Queens), 16.2, 17.1 and 18.0. It requires an SSH-based Cinder backend, such as IBM Storwize/SVC, to be actually configured, and it is not present in a default devstack. To check the setup, review the volume backend settings in cinder.conf for an SSH-based driver.

Source: bugs.launchpad.net, cve.org

How do I fix CVE-2026-133189?

The checked facts name no fixed version and no patch ids for this vulnerability. Until the vendor's advisory names a fix, the only mitigation given is to avoid or disable the affected SSH-based backend.

Source: bugs.launchpad.net, cve.org

What if there's no patch?

Avoiding or disabling the affected SSH-based backend removes this attack path. The advisory gives no other workaround.

Source: bugs.launchpad.net, cve.org

No corrections so far. Something wrong on this page? Report an error.