BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-43001High confidence

OpenStack Keystone — Incorrect Authorization

OpenStack · Keystone

7.9HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 14 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.59% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs OpenStack Keystone and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcekeystoneVendor fix publishedDebian records a fixed source-package version for this release.2:27.0.0-3+deb13u4Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcekeystoneVendor fix publishedDebian records a fixed source-package version for this release.2:22.0.2-0+deb12u3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcekeystoneVendor fix publishedDebian records a fixed source-package version for this release.2:29.0.1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcekeystoneVendor fix publishedDebian records a fixed source-package version for this release.2:29.0.1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivekeystoneVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.2:25.0.0-0ubuntu1.4Canonical Ubuntu Security ↗Source updated 6 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIkeystoneECOSYSTEM: introduced 13.0.0; last affected 29.0.1Not statedOSV record ↗aggregator derived · 10 Sep 2026
pipkeystone>= 13.0.0, <= 29.0.1Not statedGitHub advisory ↗github reviewed aggregator · 9 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-43001 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityOpenStack Keystone: OpenStack Keystone: Unauthorized cross-project access due to improper validation in EC2 credential creation
20 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.noarch as a component of Red Hat OpenStack Platform 16.2
  • openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.src as a component of Red Hat OpenStack Platform 16.2
  • python3-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.noarch as a component of Red Hat OpenStack Platform 16.2
  • openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1
  • openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost.src as a component of Red Hat OpenStack Platform 17.1
  • openstack-swift-0:2.27.1-17.1.20231004180819.el9ost.src as a component of Red Hat OpenStack Platform 17.1
  • openstack-swift-account-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1
  • openstack-swift-container-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1
  • openstack-swift-object-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1
  • openstack-swift-proxy-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1
  • openstack-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1
  • openstack-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.src as a component of Red Hat OpenStack Platform 17.1
Summary
A flaw was found in OpenStack Keystone. An attacker holding an unrestricted application credential could exploit a vulnerability in the POST /v3/credentials endpoint where the caller-supplied project_id for an EC2-type credential was not validated against the project of the authenticating application credential. This allows the attacker to create an EC2 credential targeting a different project. Subsequently, a /v3/ec2tokens exchange would issue a Keystone token scoped to the targeted project, enabling unauthorized cross-project access and lateral movement within the credential owner's role footprint.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-26488

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.

What

An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Incorrect Authorization → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-863 ↗

CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkCWE-863Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 May 2026, published on 6 May 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014000OpenStackのOpenstack Keystoneにおける不正な認証に関する脆弱性

OpenStack Keystone バージョン13から29にかけて問題が発見されました。POST /v3/credentials は、呼び出し元が提供したEC2タイプのcredential用project_idが認証中のアプリケーションcredentialのプロジェクトと一致しているかどうかを検証していませんでした。これにより、プロジェクトAの制限のないアプリケーションcredentialを持つ攻撃者が、プロジェクトBをターゲットにしたEC2 credentialを作成することが可能になりました。その後の/v3/ec2tokens交換により、元のapp_cred_idを保持しながらプロジェクトBにスコープされたKeystoneトークンが発行され、credentialの所有者が役割範囲内でプロジェクト間の横移動を行うことが可能になってしまいます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Keystone: 14.0.0 < 27.0.2, 28.0.0 < 28.0.2, 29.0.0 < 29.0.2
Fixed
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2026 · Last source change 14 Aug 2026, 12:04 UTC · CWE-863 · Incorrect Authorization

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-26488
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    openstack-keystone as a component of Red Hat OpenStack Platform 17.1; openstack-keystone.src as a component of Red Hat OpenStack Platform 17.1; python3-keystone as a component of Red Hat OpenStack Platform 17.1 · Fixed: openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.noarch as a component of Red Hat OpenStack Platform 16.2; openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.src as a component of Red Hat OpenStack Platform 16.2; python3-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.noarch as a component of Red Hat OpenStack Platform 16.2; openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost.noarch as a component of Red Hat OpenStack Services on OpenShift 18.0; openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost.src as a component of Red Hat OpenStack Services on OpenShift 18.0; python3-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost.noarch as a component of Red Hat OpenStack Services on OpenShift 18.0
    After
    Fixed: openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.noarch as a component of Red Hat OpenStack Platform 16.2; openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.src as a component of Red Hat OpenStack Platform 16.2; python3-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost.noarch as a component of Red Hat OpenStack Platform 16.2; openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost.src as a component of Red Hat OpenStack Platform 17.1; openstack-swift-0:2.27.1-17.1.20231004180819.el9ost.src as a component of Red Hat OpenStack Platform 17.1; openstack-swift-account-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-swift-container-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-swift-object-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-swift-proxy-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.src as a component of Red Hat OpenStack Platform 17.1; openstack-tempest-all-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; python3-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; python3-swift-0:2.27.1-17.1.20231004180819.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; python3-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; python3-tempest-tests-1:33.0.0-17.1.20260406141650.1580f6f.el9ost.noarch as a component of Red Hat OpenStack Platform 17.1; openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost.noarch as a component of Red Hat OpenStack Services on OpenShift 18.0; openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost.src as a component of Red Hat OpenStack Services on OpenShift 18.0; python3-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost.noarch as a component of Red Hat OpenStack Services on OpenShift 18.0
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    14.0.0 < 27.0.2; 28.0.0 < 28.0.2; 29.0.0 < 29.0.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    14.0.0 < 27.0.2; 28.0.0 < 28.0.2; 29.0.0 < 29.0.2 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-26488↗Red Hat Product Security security advisory↗Public exploit reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-43001 · cve.blacktree.nl