7.9

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-43001

CVE-2026-43001: OpenStack Keystone has an Incorrect Authorization Issue

An issue was discovered in OpenStack Keystone 13 through 29. 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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-43001

CVE-2026-43001:

7.9

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
keystone	pip	>= 13.0.0, <= 29.0.1

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists in OpenStack Keystone because of a missing authorization check when creating and using EC2-type credentials with an application credential. The root cause is twofold:

Credential Creation: The POST /v3/credentials endpoint, handled by the CredentialResource.post function, failed to validate that the project_id in the request body for a new EC2 credential was the same as the project_id of the application credential used to authenticate the request. This allowed an attacker with an application credential for Project A to create an EC2 credential associated with Project B.
Token Exchange: When the specially crafted EC2 credential was used to get a token via the POST /v3/ec2tokens endpoint, the EC2_S3_Resource.handle_authenticate function would issue a token. This function also lacked a check to ensure the project of the EC2 credential and the application credential matched. As a result, it would issue a token scoped to Project B, even though the original authentication was based on an application credential for Project A.

The patch addresses both of these issues by adding the necessary validation checks in both CredentialResource.post and EC2_S3_Resource.handle_authenticate, thus preventing the creation of mismatched credentials and the issuance of improperly scoped tokens.

Vulnerable functions

CredentialResource.post

keystone/api/credentials.py

This function is responsible for creating credentials. It was vulnerable because it did not validate that the `project_id` provided for a new EC2 credential matched the `project_id` of the application credential used for authentication. This allowed an attacker to create a credential for a project they were not authorized for.

EC2_S3_Resource.handle_authenticate

keystone/api/_shared/EC2_S3_Resource.py

This function handles the authentication process for EC2 tokens. It was vulnerable because it did not verify that the project associated with the EC2 credential matched the project of the linked application credential. This allowed an attacker who had created a malicious EC2 credential to obtain a Keystone token scoped to a different project, leading to cross-project lateral movement.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.