dbcve.org
VitrageApplication · Openstack

CVE-2026-28370

CRITICAL · 9.1 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 12.01 / 13.0.1 or later.
See remediation →
97/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the query parser in OpenStack Vitrage before 12.0.1, 13.0.0, 14.0.0, and 15.0.0, a user allowed to access the Vitrage API may trigger code execution on the Vitrage service host as the user the Vitrage service runs under. This may result in unauthorized access to the host and further compromise of the Vitrage service. All deployments exposing the Vitrage API are affected. This occurs in _create_query_function in vitrage/graph/query.py.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VitrageApplication
Affected:< 12.01>= 13.0.0, < 13.0.1>= 14.0.0, < 14.0.1>= 15.0.0, < 15.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.01 / 13.0.1 / 14.0.1 or later
Fixed in 12.0113.0.114.0.1
Recommended fix High confidence

12.0.1 (for 12.x branch), 13.0.1 (for 13.x branch), 14.0.1 (for 14.x branch), or 15.0.1 (for 15.x branch)

  1. 1. Identify the currently installed Vitrage version by checking the package manager or running 'vitrage --version'
  2. 2. Determine which version branch you are running (12.x, 13.x, 14.x, or 15.x)
  3. 3. For Vitrage 12.x: Upgrade to version 12.0.1 or later using the package manager (e.g., pip install --upgrade vitrage==12.0.1 or equivalent)
  4. 4. For Vitrage 13.x: Upgrade to version 13.0.1 or later
  5. 5. For Vitrage 14.x: Upgrade to version 14.0.1 or later
  6. 6. For Vitrage 15.x: Upgrade to version 15.0.1 or later
  7. 7. After upgrading, restart the Vitrage service to load the patched code
  8. 8. Verify the upgrade was successful by checking the installed version
Caveat Minor version upgrades within the same major series typically have no breaking changes; however, review the release notes for any configuration or API changes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28370 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data