CVE-2026-43001: [OSSA-2026-015] OpenStack Keystone: Multiple cdential delegation and authorization bypass vulnerabilities (CVE-2026-42998, CVE-2026-42999, CVE-2026-43000, CVE-2026-43001, CVE-2026-44394)

Published May 1, 2026
·
Updated

An issue was discovered in OpenStack Keystone 13 through 29. POST /v3/credentials did not validate that the caller-supplied projectid 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 appcredid, enabling cross-project lateral movement within the credential owner's role footprint.

Other sources

An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied projectid 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 appcredid, enabling cross-project lateral movement within the credential owner's role footprint.

Debian

Affected Software

5 affected componentsFixes available
Openstack Keystone>=13<=29
Openstack Keystone>=14.0.0<27.0.2
Openstack Keystone>=28.0.0<28.0.2
Openstack Keystone>=29.0.0<29.0.2
debian/keystone<=2:18.0.0-3+deb11u1, <=2:22.0.2-0+deb12u1, <=2:27.0.0-3+deb13u1
2:18.1.0-1+deb11u32:22.0.2-0+deb12u32:27.0.0-3+deb13u42:29.0.1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/keystone to a version that resolves this vulnerability.

    Fixed in 2:18.1.0-1+deb11u3Fixed in 2:22.0.2-0+deb12u3Fixed in 2:27.0.0-3+deb13u4Fixed in 2:29.0.1-2
  2. Upgrade

    Upgrade openstack/keystone to a version that resolves this vulnerability.

    Fixed in 29.0.2Patch OSSA-2026-015
  3. Upgrade

    Upgrade openstack/keystone to a version that resolves this vulnerability.

    Fixed in 29.0.1Patch OSSA-2026-015

Event History

May 1, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·09:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 17, 2026
Data Sourced
via Ubuntu·08:41 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·08:42 PM
DescriptionAffected Software
Data Sourced
via Launchpad·08:42 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-43001?

CVE-2026-43001 is considered a high severity vulnerability due to the potential for unauthorized access to project credentials.

2

How do I fix CVE-2026-43001?

To fix CVE-2026-43001, upgrade OpenStack Keystone to a version newer than 29, where the issue has been resolved.

3

What versions of OpenStack Keystone are affected by CVE-2026-43001?

OpenStack Keystone versions 13 through 29 are affected by CVE-2026-43001.

4

What impact does CVE-2026-43001 have on application security?

CVE-2026-43001 could allow attackers to exploit unrestricted credentials, compromising the integrity of the project associated with them.

5

Is there a workaround for CVE-2026-43001 if upgrading is not possible?

There are no documented workarounds for CVE-2026-43001; the best mitigation is to apply the necessary upgrades.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203