Critical Vulnerability in Keystone Package: CVE-2026-43000

keystone Updated 22 Oct 2026

Summary

28/05/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-43000: ... Affects keystone versions 2:18.0.0-3 – 2:29.0.1-2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Keystone is an open-source identity service used in cloud computing environments, particularly within OpenStack. It provides authentication and authorization services for users and services, enabling secure access to resources. Keystone is essential for managing users, roles, and permissions in a cloud infrastructure. However, recent findings have revealed a vulnerability (CVE-2026-43000) that affects multiple Debian distributions, potentially compromising the security of systems relying on this package.

Vulnerability Detail

CVE-2026-43000 is a critical vulnerability identified in the Keystone package, which could allow unauthorized access to sensitive resources. The vulnerability originates from improper validation of user inputs, leading to potential privilege escalation or unauthorized data access. If exploited, attackers could manipulate Keystone's authentication mechanisms, resulting in severe security breaches within cloud environments. The vulnerability affects Keystone versions across multiple Debian distributions, including Bullseye, Bookworm, Trixie, and Forky.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users may consider implementing stricter access controls and monitoring user activities within Keystone until a patch is applied. This can help mitigate the risk of unauthorized access while waiting for an official fix.

Conclusion

CVE-2026-43000 poses a significant risk to users of the Keystone package across multiple Debian distributions. It is crucial for users to update their installations to the latest patched version to safeguard their systems. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure timely alerts for any potential threats.

See every vulnerability recorded for keystone →

Share this vulnerability

FAQ

CVE-2026-43000 is a critical vulnerability in the Keystone package that could allow unauthorized access to sensitive resources in cloud environments.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability without requiring signup.

If exploited, this vulnerability could lead to unauthorized data access, privilege escalation, and severe security breaches within cloud infrastructures.

Yes, a patched version of the Keystone package is available. Users should update their Keystone installation to the latest version to mitigate the vulnerability.

If immediate updates are not possible, consider applying stricter access controls and monitoring user activities within Keystone as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for keystone.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback