dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-65073

HIGH · 7.5 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenStack Keystone versions before 26.0.1, 27.0.0, and 28.0.0 contain an authentication bypass in the /v3/ec2tokens and /v3/s3tokens endpoints. These endpoints, intended for AWS Signature validation in cross-cloud authentication scenarios, incorrectly accept valid AWS signatures to obtain full Keystone authorization tokens. An attacker with AWS-style credentials can exploit this to gain unauthorized access to OpenStack resources.

MitigationUpgrade Keystone to version 26.0.1, 27.0.0, or 28.0.0 to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Keystone version
    Query the Keystone API version endpoint (GET /v3/) or check the installed package version using the package manager (e.g., dpkg -l python-keystone or rpm -q python-keystone). Compare against the affected versions: before 26.0.1, version 27.0.0, and before 28.0.0.
    Affected if The installed Keystone version is lower than 26.0.1, is exactly 27.0.0, or is lower than 28.0.0 (e.g., 27.x).
  2. Verify ec2tokens endpoint is exposed
    Review the Keystone service configuration files (typically in /etc/keystone/) or the API endpoint catalog. Alternatively, send a test request to the /v3/ec2tokens endpoint and observe if it accepts the request.
    Affected if The /v3/ec2tokens endpoint is enabled and accessible in the environment.
  3. Verify s3tokens endpoint is exposed
    Review the Keystone service configuration files or the API endpoint catalog. Alternatively, send a test request to the /v3/s3tokens endpoint and observe if it accepts the request.
    Affected if The /v3/s3tokens endpoint is enabled and accessible in the environment.
  4. Check for AWS-style credentials in the environment
    Review the Keystone credential database or configuration for any stored AWS-style access keys or secret keys that could be used to exploit the vulnerable endpoints.
    Affected if AWS-compatible credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY style) are present in the Keystone configuration or credential store.

If Keystone version is affected (before 26.0.1, exactly 27.0.0, or before 28.0.0) AND either the /v3/ec2tokens or /v3/s3tokens endpoint is exposed, the environment is vulnerable to authentication bypass via AWS signature validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Keystone to version 26.0.1, 27.0.0, or 28.0.0 to remediate this vulnerability.

Recommended fix High confidence

OpenStack Keystone 26.0.1 (for 26.x branch), 27.0.0 (for 27.x branch), or 28.0.0 (for 28.x branch)

  1. 1. Identify the currently deployed OpenStack Keystone version by checking the package version or Keystone service configuration
  2. 2. Determine which stable branch is in use (likely 26.x, 27.x, or 28.x)
  3. 3. If using branch 26.x, upgrade to Keystone 26.0.1 or later
  4. 4. If using branch 27.x, upgrade to Keystone 27.0.0 or later
  5. 5. If using branch 28.x, upgrade to Keystone 28.0.0 or later
  6. 6. Verify the upgrade by checking that /v3/ec2tokens and /v3/s3tokens endpoints no longer return full Keystone authorization tokens
  7. 7. Test existing EC2/S3 credential workflows to ensure they still function correctly post-upgrade
Caveat Review OpenStack release notes for the target version to check for configuration or API changes that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65073 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data