Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65073: CWE-863 Incorrect Authorization in OpenStack Keystone

0
High
VulnerabilityCVE-2025-65073cvecve-2025-65073cwe-863
Published: Mon Nov 17 2025 (11/17/2025, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: OpenStack
Product: Keystone

Description

OpenStack Keystone before 26.0.1, 27.0.0, and 28.0.0 allows a /v3/ec2tokens or /v3/s3tokens request with a valid AWS Signature to provide Keystone authorization.

AI-Powered Analysis

AILast updated: 11/17/2025, 07:46:28 UTC

Technical Analysis

CVE-2025-65073 is a security vulnerability identified in OpenStack Keystone, the identity service component of the OpenStack cloud platform. Specifically, versions prior to 26.0.1, 27.0.0, and 28.0.0 are affected. The vulnerability allows an attacker to authenticate to Keystone by submitting requests to the /v3/ec2tokens or /v3/s3tokens endpoints using a valid AWS Signature. Normally, Keystone requires proper authentication tokens or credentials, but this flaw permits authorization solely based on the presence of a valid AWS Signature, effectively bypassing standard Keystone authentication controls. This means that if an attacker can generate or obtain a valid AWS Signature, they can impersonate users or services within the OpenStack environment. The vulnerability impacts the confidentiality and integrity of the cloud environment by potentially allowing unauthorized access to identity tokens, which can be used to escalate privileges or access sensitive cloud resources. Although no known exploits have been reported in the wild, the vulnerability is critical because Keystone is central to managing authentication and authorization in OpenStack clouds. The lack of a CVSS score suggests the vulnerability is newly published and not yet fully assessed. Exploitation requires possession of valid AWS signing credentials or keys, which may limit the attack surface but does not eliminate risk. The vulnerability affects multiple OpenStack versions, indicating a broad potential impact across deployments. Remediation involves upgrading to the fixed versions of Keystone (26.0.1, 27.0.0, or 28.0.0) once available and reviewing AWS credential management practices to prevent unauthorized signature generation.

Potential Impact

For European organizations, the impact of CVE-2025-65073 is significant due to the widespread use of OpenStack in private and public cloud infrastructures across Europe. Unauthorized Keystone authorization can lead to identity token compromise, enabling attackers to impersonate legitimate users or services. This can result in unauthorized access to cloud resources, data breaches, privilege escalation, and disruption of cloud services. Organizations relying on OpenStack for critical workloads, including government, finance, healthcare, and telecommunications sectors, face increased risk of operational disruption and data loss. The vulnerability could also undermine trust in cloud services and complicate compliance with European data protection regulations such as GDPR. Since exploitation requires valid AWS signatures, attackers might target AWS credential theft or misuse, increasing the risk of multi-cloud compromise scenarios. The absence of known exploits provides a window for proactive mitigation, but the potential impact on confidentiality, integrity, and availability remains high if exploited.

Mitigation Recommendations

1. Upgrade OpenStack Keystone to versions 26.0.1, 27.0.0, or 28.0.0 as soon as patches are released to address this vulnerability. 2. Conduct a thorough audit of AWS credentials and signing keys used within the organization to ensure they have not been compromised or misused. 3. Implement strict access controls and monitoring around AWS credential usage, including rotating keys regularly and enforcing least privilege principles. 4. Monitor Keystone logs and API access patterns for unusual or unauthorized /v3/ec2tokens or /v3/s3tokens requests that could indicate exploitation attempts. 5. Employ network segmentation and firewall rules to restrict access to Keystone endpoints to trusted systems only. 6. Educate cloud administrators and security teams about this vulnerability and the importance of credential security. 7. Consider deploying additional identity and access management (IAM) controls or multi-factor authentication to reduce the risk of unauthorized access. 8. Engage in threat hunting activities focused on detecting anomalous AWS signature usage within the cloud environment. 9. Coordinate with cloud service providers and vendors for timely updates and security advisories related to OpenStack Keystone.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-17T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 691ad1de77ef4e346a475a5d

Added to database: 11/17/2025, 7:42:22 AM

Last enriched: 11/17/2025, 7:46:28 AM

Last updated: 11/17/2025, 2:06:29 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats