OpenStack Patches Cinder LIO iSCSI Path Traversal and Privilege Escalation

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Identify Cinder volume hosts using LIO iSCSI and apply the supported branch-specific patch or a distributor update that includes it. Validate host permissions and volume attachment workflows.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Cinder package versions, release branches, volume backends, configured iSCSI target drivers and the owners of each volume host. Match the exact version ranges and confirm LIO iSCSI is in use. The advisory requires an authenticated member user; other target drivers are outside its stated scope. LIO is typically paired with the LVM volume driver. Use the project-linked patch for the installed supported branch or the distribution-maintained package that incorporates it. Confirm backport status with the provider before relying on a package version string. Test legitimate volume initialization, attach and detach operations and rejection of invalid initiator input in a controlled environment. Review relevant API and host audit logs, and preserve package provenance, patch identifiers and change evidence.

Open the authoritative advisory

Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeOpenStack Cinder volume hosts using the LIO iSCSI target driver
AdvisoryOSSA-2026-051
CVEsA CVE was requested from MITRE and has not been assigned in the cited advisory.
Authoritative release date2026-11-17T13:03:42Z — original OpenStack project announcement; the advisory page separately states November 17, 2026.
Authority revision dateNo separate material revision is confirmed.
Affected versionsCinder before 27.1.1; 28.0.0 through versions before 28.1.1; and 29.0.0 through versions before 29.1.1. Only hosts using the LIO iSCSI target driver are affected.
Fixed versionApply the linked patch for the supported branch; the advisory gives unaffected boundaries of 27.1.1, 28.1.1 and 29.1.1 for the corresponding release lines
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe project advisory does not state that exploitation has occurred in the wild.; no exploitation claim is inferred.

What Changed

OSSA-2026-051 discloses path traversal through the connector initiator in an os-initialize_connection request. An authenticated user with the member role can create or overwrite files on a vulnerable volume host.

What To Validate Now

  1. Inventory. Record Cinder package versions, release branches, volume backends, configured iSCSI target drivers and the owners of each volume host.
  2. Establish applicability. Match the exact version ranges and confirm LIO iSCSI is in use. The advisory requires an authenticated member user; other target drivers are outside its stated scope. LIO is typically paired with the LVM volume driver.
  3. Remediate. Use the project-linked patch for the installed supported branch or the distribution-maintained package that incorporates it. Confirm backport status with the provider before relying on a package version string.
  4. Validate. Test legitimate volume initialization, attach and detach operations and rejection of invalid initiator input in a controlled environment. Review relevant API and host audit logs, and preserve package provenance, patch identifiers and change evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

The project supplies a courtesy patch for unmaintained 2025.1, which receives no new releases. Do not assume a patch link means a packaged release is available. Preserve volume-service availability and a recovery path during maintenance; investigate suspicious host writes through the incident process.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Original project announcement and release timestamp

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.