cve.bz

CVE-2026-93856 openstack cinder

4.3 mediumEPSS 0.4%

Medium (4.3) in openstack cinder. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
In OpenStack Cinder through 29.0.0, cross-project information disclosure can occur in the Messages API. A non-admin user with the project-scoped 'member' or 'reader' role making the Block Storage API v3.3 "List messages" call finds the non-expired user messages for other projects included in the response, resulting in the leakage of UUIDs of resources owned by other projects, in addition to the user message about the other projects' resources (which, by design, are sanitized generic messages). All Cinder deployments are affected.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-669 Incorrect Resource Transfer Between Spheres
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-93856 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93856?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93856?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93856 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-93856

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-93856](https://cve.bz/cve/badge/CVE-2026-93856.svg)](https://cve.bz/cve/CVE-2026-93856)

HTML:

<a href="https://cve.bz/cve/CVE-2026-93856"><img src="https://cve.bz/cve/badge/CVE-2026-93856.svg" alt="CVE-2026-93856"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenStack Cinderfrom 9.0.0 before 26.3.1
OpenStack Cinder27.0.0
OpenStack Cinder28.0.0
OpenStack Cinder29.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13cinderno fix listedDEBIAN-CVE-2026-93856
Debian14cinder2:29.0.0-3DEBIAN-CVE-2026-93856
Ubuntu16.04:LTS, 20.04:LTS, 22.04:LTS and 4 morecinderno fix listedUBUNTU-CVE-2026-93856

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having Moderate impact by Red Hat because an authenticated user with project-level access can list Cinder user messages that belong to other projects. The response contains predefined, sanitized error text and resource identifiers. It does not include the owning project ID, so the caller cannot tell which project a resource identifier belongs to. Cinder records these messages for errors, not for successful operations. The issue does not expose volume contents and does not allow modification or deletion of other tenants' resources.

Red Hat's mitigation

Operators can shorten how long these messages remain available by lowering the Cinder message_ttl option. The default is 2592000 seconds (30 days). A periodic task removes expired messages. That task runs on the message_reap_interval, which defaults to 86400 seconds (24 hours). This reduces the window during which another project's error messages can be listed. It does not prevent the list API from returning messages that have not yet expired.

ProductPackageStateAdvisory
Red Hat OpenStack Platform 13 (Queens)openstack-cinderFix deferred
Red Hat OpenStack Platform 16.2openstack-cinderFix deferred
Red Hat OpenStack Platform 17.1openstack-cinderFix deferred
Red Hat OpenStack Platform 18.0openstack-cinderFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-93856.

References

Check your stackJSON