External risk intelligence

OpenStack Cinder SSH Storage Driver Command Injection

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-133189

The vulnerability exists in OpenStack Cinder's SSH-based storage-driver support. Exploitation requires an authenticated user who already owns a volume on the backend to interact with the storage array's management interface. Because this requires established authenticated access and backend-specific configuration, it is unlikely to be exposed directly to the public internet in common deployments.

OS Command Injection

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A command injection vulnerability has been identified in OpenStack Cinder's SSH-based storage driver. This flaw could allow an authenticated user with volume ownership to inject commands into the storage array's management interface, potentially leading to the disclosure of storage configurations or unauthorized changes affecting other tenants' storage.

  • Command injection in OpenStack storage drivers.
  • Affects storage integrity and availability.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this by leveraging an existing authenticated user account that already owns a volume. This user would then craft specific connection details to inject commands into the storage management interface, potentially leading to the disclosure of sensitive storage information or unauthorized modifications affecting other users' storage.

  • Authenticated user with volume ownership.
  • Crafted connection data for command injection.
  • Risk of data disclosure or modification.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user owning a volume could inject commands into the storage array's management interface by supplying crafted connection information. This could expose storage configuration details or, if the Cinder backend account has administrative rights, lead to modifications affecting other tenants' storage integrity or availability.

  • Storage configuration information at risk.
  • Commands injected via crafted connection info.
  • Affects storage integrity and availability.

Operational Fix

Recommended remediation, mitigation, and detection steps

This command injection vulnerability in OpenStack Cinder's SSH-based storage driver likely impacts platform or infrastructure teams responsible for managing storage backends, as well as security teams overseeing access controls and the vendor-management team coordinating with OpenStack. The first practical step involves identifying all Cinder backends using SSH, confirming their reachability and criticality, and then engaging with the accountable platform or infrastructure owner to plan remediation.

  • Platform and infrastructure teams own.
  • Verify SSH storage backend reachability.
  • Plan targeted remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is OpenStack Cinder?

OpenStack Cinder is the block storage service for OpenStack clouds. It provides persistent storage volumes that users can attach to virtual machines. The affected component specifically involves the drivers Cinder uses to communicate with storage hardware via SSH, acting as the bridge between the cloud platform and the underlying physical storage arrays.

What does CVE-2026-133189 mean?

This CVE describes a command injection vulnerability, classified as CWE-78. It occurs when a program passes unsanitized input to a system shell. In this case, Cinder fails to properly validate shell metacharacters in connection information. Consequently, a user can supply specially crafted data that the storage array mistakenly interprets as executable commands.

How does an attacker trigger this vulnerability?

Triggering this bug requires the attacker to be an authenticated user who already owns a volume on the targeted storage backend. They must provide malicious connection details that Cinder then processes. Simply having access to the OpenStack API is not enough; the attacker must be able to interact with the specific backend storage configuration through the driver.

Is my environment at risk from this CVE?

Halo Surface Signal indicates that direct internet exposure is unlikely for this issue. Because exploitation requires an existing, authenticated user account and specific backend configurations to reach the storage array's management interface, the vulnerability is generally contained within the internal infrastructure rather than being directly reachable from the public web.

How should I respond to this threat?

Start by auditing your OpenStack infrastructure to identify all storage backends configured to use the SSH-based driver. Once these systems are mapped, coordinate with your platform or infrastructure teams to review access controls and monitor for any suspicious configuration changes or storage management activity until a formal vendor update is applied.

References