Medium

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

  • Disclosed: 28.05.2026
  • Updated: 11.10.2026 15:17

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 handle_scoped_token() function in the mapped authentication plugin returns response data without an expires_at 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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) keystone >= 14.0.0, < 27.0.2, >= 28.0.0, < 28.0.2, >= 29.0.0, < 29.0.2 27.0.2, 28.0.2, 29.0.2

References

CVSS score 6/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
Weakness (CWE)
CWE-863
Platform
Python (PyPI)
Package
keystone
Disclosed
28.05.2026
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-603 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-whqr-fgm5-x77q - CC BY 4.0

Vulnerability history: keystone

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (42) in the archive
Total entries
42
First → latest
09.2012 05.2026
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 18
  • Medium 21
  • Low 1
  • Unrated 1

Disclosures per year

  1. 2017: 0
  2. 2018: 2
  3. 2019: 1
  4. 2020: 4
  5. 2021: 0
  6. 2022: 14
  7. 2023: 0
  8. 2024: 0
  9. 2025: 1
  10. 2026: 7

earlier: 13

Severity:
  1. OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token this entry
    Medium · 6.0 CVE-2026-44394 >= 14.0.0, < 27.0.2, >= 28.0.0, < 28.0.2, >= 29.0.0, < 29.0.2 27.0.2, 28.0.2, 29.0.2
  2. High · 7.9 CVE-2026-43001 >= 13.0.0, <= 29.0.1 no fix
  3. High · 7.5 CVE-2025-65073 < 26.0.1, >= 27.0.0.0rc1, < 27.0.0, >= 28.0.0.0rc1, < 28.0.0 26.0.1, 27.0.0, 28.0.0
  4. Critical · 9.1 CVE-2021-3563 <= 21.0.0 no fix
  5. High · 7.5 CVE-2021-38155 >= 10.0, < 16.0.2, >= 17.0, < 17.0.1, >= 18.0, < 18.0.1, >= 19.0, < 19.0.1 16.0.2, 17.0.1, 18.0.1, 19.0.1
  6. High CVE-2012-4456 >= 2012.1, < 2012.1.2 2012.1.2
  7. High · 8.8 CVE-2020-12690 < 15.0.1, >= 16.0.0.0rc1, < 16.0.0 15.0.1, 16.0.0
  8. High · 7.5 CVE-2015-7546 >= 8.0, < 8.1.0, >= 9.0.0.0b1, < 9.0.0.0b2 8.1.0, 9.0.0.0b2
  9. High · 6.5 CVE-2014-5253 < 8.0.0a0 8.0.0a0
  10. High · 7.5 CVE-2012-3542 < 2012.1 2012.1

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.