Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token

CVE-2026-44394GHSA-whqr-fgm5-x77q

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-44394: 0.25% estimated exploitation activity in the next 30 days; percentile 16.31 (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 federated token rescoping mechanism does not propagate the original token's expiry to the newly issued token. When a federated user rescopes a token via POST /v3/auth/tokens, the handlescopedtoken() function in the mapped authentication plugin returns response data without an expiresat value. The token provider falls back to issuing a token with a fresh default TTL. By rescoping repeatedly before each token expires, a user can maintain access indefinitely, bypassing operator-configured token lifetime policies. This is a variant of CVE-2012-3426. Only deployments using federated identity (SAML2, OpenID Connect) are affected.

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

    Amended from ghsa record GHSA-whqr-fgm5-x77q

  2. Revision 1 · created ·

    Published from osv record GHSA-whqr-fgm5-x77q

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-44394

Advisory: OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token
IDs: CVE-2026-44394, GHSA-whqr-fgm5-x77q
Record: https://patchnext.com/advisories/cve-2026-44394 (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-whqr-fgm5-x77q (OSV record GHSA-whqr-fgm5-x77q lists affected ranges: PyPI keystone >=14.0.0 =28.0.0 =29.0.0 <29.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-whqr-fgm5-x77q (GitHub-reviewed advisory GHSA-whqr-fgm5-x77q 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…