Unauthenticated account access via reusable AWS signatures
Published Nov 17, 2025 · Updated Nov 17, 2025
Incorrect authorization in OpenStack Keystone before 26.0.1, 27.0.0, and 28.0.0 allows remote attackers to obtain Keystone authorization. The EC2 and S3 token APIs validate an AWS signature without establishing that it was intended for that Keystone request, so a presigned S3 URL signature is reusable. Unauthenticated endpoint reachability and a valid signature are required; EC2 can issue a fully scoped token, while S3 discloses accepted scope.
Summary
What happened
Incorrect authorization in OpenStack Keystone before 26.0.1, 27.0.0, and 28.0.0 allows remote attackers to obtain Keystone authorization. The EC2 and S3 token APIs validate an AWS signature without establishing that it was intended for that Keystone request, so a presigned S3 URL signature is reusable. Unauthenticated endpoint reachability and a valid signature are required; EC2 can issue a fully scoped token, while S3 discloses accepted scope.
The record
- CVE
- CVE-2025-65073
- Published
- Nov 17, 2025
- Updated
- Nov 17, 2025
- Vendor
- OpenStack
- Product
- Keystone
- Classifications
- CWE-863, T1528, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 17, 2025CVE publishedPublication date reported by the CVE source.
- Nov 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.0.1
- Affected versionversion=27.0.0
- Affected versionversion=28.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- s3tokens.pyfunctional · demonstrated
- ec2tokens.pyfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo