Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

OpenStack Keystone doesn't verify that the user supplied in the authentication request matches the owner of the application credential

CVE-2026-42998GHSA-8f8m-wrvr-wcvf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (keystone 29.0.2, 28.0.2, 27.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI keystone

    Affected
    >= 14.0.0, < 27.0.2>= 28.0.0, < 28.0.2>= 29.0.0, < 29.0.2
    Fixed in
    27.0.2, 28.0.2, 29.0.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.0 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS
  • CVE-2026-42998: 0.30% estimated exploitation activity in the next 30 days; percentile 23.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone application credential authentication plugin does not verify that the user supplied in the authentication request matches the owner of the application credential. An attacker can authenticate with their own application credential ID and secret while specifying a different user's name and domain in the request body. Keystone issues a token attributed to the victim user. The impersonated token is project-scoped and carries the intersection of the application credential's roles and the victim's actual roles on the project. This enables audit evasion, reading the victim's credentials, and acting as the victim within shared projects.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8f8m-wrvr-wcvf

  2. Revision 1 · created ·

    Published from osv record GHSA-8f8m-wrvr-wcvf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42998

Advisory: OpenStack Keystone doesn't verify that the user supplied in the authentication request matches the owner of the application credential
IDs: CVE-2026-42998, GHSA-8f8m-wrvr-wcvf
Record: https://patchnext.com/advisories/cve-2026-42998 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keystone 29.0.2, 28.0.2, 27.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI keystone: affected >= 14.0.0, < 27.0.2; >= 28.0.0, < 28.0.2; >= 29.0.0, < 29.0.2; fixed in 27.0.2, 28.0.2, 29.0.2

## Suggested inspection (read-only)
- `python -m pip show keystone`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on keystone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8f8m-wrvr-wcvf (OSV record GHSA-8f8m-wrvr-wcvf lists affected ranges: PyPI keystone >=14.0.0 =28.0.0 =29.0.0 <29.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-8f8m-wrvr-wcvf (GitHub-reviewed advisory GHSA-8f8m-wrvr-wcvf lists affected ranges: PyPI keystone >=14.0.0 =28.0.0 =29.0.0 <29.0.2)

Commands are suggestions: review each one before running it.

Loading voting…