keystone - Debian Package Tracker

general

source: keystone (main)
version: 2:29.0.1-2
maintainer: Debian OpenStack (DMD)
uploaders: Michal Arbet [DMD] – Thomas Goirand [DMD]
arch: all
std-ver: 4.4.1
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2:18.0.0-3+deb11u1
o-o-sec: 2:18.1.0-1+deb11u3
oldstable: 2:22.0.2-0+deb12u3
old-sec: 2:22.0.2-0+deb12u3
old-p-u: 2:22.0.2-0+deb12u3
stable: 2:27.0.0-3+deb13u4
stable-sec: 2:27.0.0-3+deb13u4
testing: 2:29.0.1-2
unstable: 2:29.0.1-2

versioned links

2:18.0.0-3+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:18.1.0-1+deb11u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:22.0.2-0+deb12u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:27.0.0-3+deb13u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:29.0.1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

keystone
keystone-doc
python3-keystone

action needed

Marked for autoremoval on 18 September due to httpcore, ipywidgets, python-repoze.who, towncrier: #1143321, #1143428, #1143694, #1144575 high

Version 2:29.0.1-2 of keystone is marked for autoremoval from testing on Fri 18 Sep 2026. It depends (transitively) on httpcore, ipywidgets, python-repoze.who, towncrier, affected by #1143321, #1143428, #1143694, #1144575. You should try to prevent the removal by fixing these RC bugs.

Created: 2026-08-01 Last update: 2026-08-27 09:02

A new upstream version is available: 29.0.2 high

A new upstream version 29.0.2 is available, you should consider packaging it.

Created: 2026-07-03 Last update: 2026-08-27 08:30

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2026-80182: In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
CVE-2026-80184: In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

Created: 2026-08-26 Last update: 2026-08-26 09:30

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2026-80182: In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
CVE-2026-80184: In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

Created: 2026-08-26 Last update: 2026-08-26 09:30

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-80182: In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
CVE-2026-80184: In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

Created: 2026-08-26 Last update: 2026-08-26 09:30

3 security issues in bullseye high

There are 3 open security issues in bullseye.

2 important issues:

CVE-2026-80182: In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
CVE-2026-80184: In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

1 issue postponed or untriaged:

CVE-2021-3563: (needs triaging) A flaw was found in openstack-keystone. Only the first 72 characters of an application secret are verified allowing attackers bypass some password complexity which administrators may be counting on. The highest threat from this vulnerability is to data confidentiality and integrity.

Created: 2026-08-26 Last update: 2026-08-26 09:30

3 security issues in bookworm high

There are 3 open security issues in bookworm.

2 important issues:

CVE-2026-80182: In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
CVE-2026-80184: In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

1 issue postponed or untriaged:

CVE-2021-3563: (needs triaging) A flaw was found in openstack-keystone. Only the first 72 characters of an application secret are verified allowing attackers bypass some password complexity which administrators may be counting on. The highest threat from this vulnerability is to data confidentiality and integrity.

Created: 2026-08-26 Last update: 2026-08-26 09:30

lintian reports 13 warnings normal

Lintian reports 13 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-04-10 Last update: 2026-05-29 09:01

debian/patches: 8 patches to forward upstream low

Among the 10 debian patches available in version 2:29.0.1-2 of the package, we noticed the following issues:

8 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-05-29 06:47

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2026-01-14 11:30

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.4.1).

Created: 2020-01-21 Last update: 2026-05-28 22:37

news

[rss feed]

[2026-08-27] Accepted keystone 2:29.0.2-1 (source) into unstable (Thomas Goirand)
[2026-06-08] Accepted keystone 2:27.0.0-3+deb13u4 (source) into proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
[2026-06-08] Accepted keystone 2:22.0.2-0+deb12u3 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
[2026-06-08] Accepted keystone 2:27.0.0-3+deb13u4 (source) into stable-security (Debian FTP Masters) (signed by: Thomas Goirand)
[2026-06-08] Accepted keystone 2:22.0.2-0+deb12u3 (source) into oldstable-security (Debian FTP Masters) (signed by: Thomas Goirand)
[2026-05-31] keystone 2:29.0.1-2 MIGRATED to testing (Debian testing watch)
[2026-05-28] Accepted keystone 2:29.0.1-2 (source) into unstable (Thomas Goirand)
[2026-05-28] Accepted keystone 2:18.1.0-1+deb11u3 (source) into oldoldstable-security (Thomas Goirand)
[2026-05-22] Accepted keystone 2:22.0.2-0+deb12u2 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
[2026-05-22] Accepted keystone 2:27.0.0-3+deb13u3 (source) into proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
[2026-04-19] keystone 2:29.0.1-1 MIGRATED to testing (Debian testing watch)
[2026-04-17] Accepted keystone 2:29.0.1-1 (source) into unstable (Thomas Goirand)
[2026-04-15] keystone 2:29.0.0-3 MIGRATED to testing (Debian testing watch)
[2026-04-13] Accepted keystone 2:29.0.0-3 (source) into unstable (Thomas Goirand)
[2026-04-12] keystone 2:29.0.0-2 MIGRATED to testing (Debian testing watch)
[2026-04-10] Accepted keystone 2:29.0.0-2 (source) into unstable (Thomas Goirand)
[2026-04-03] keystone 2:29.0.0-1 MIGRATED to testing (Debian testing watch)
[2026-04-01] Accepted keystone 2:29.0.0-1 (source) into unstable (Thomas Goirand)
[2026-03-31] keystone 2:29.0.0~rc1-2 MIGRATED to testing (Debian testing watch)
[2026-03-27] Accepted keystone 2:29.0.0~rc1-2 (source) into unstable (Thomas Goirand)
[2026-03-16] Accepted keystone 2:29.0.0~rc1-1 (source) into experimental (Thomas Goirand)
[2026-02-21] keystone 2:28.0.0-6 MIGRATED to testing (Debian testing watch)
[2026-02-16] Accepted keystone 2:28.0.0-6 (source) into unstable (Thomas Goirand)
[2026-01-15] keystone 2:28.0.0-5 MIGRATED to testing (Debian testing watch)
[2026-01-13] Accepted keystone 2:28.0.0-5 (source) into unstable (Thomas Goirand)
[2025-12-11] keystone 2:28.0.0-4 MIGRATED to testing (Debian testing watch)
[2025-12-07] Accepted keystone 2:28.0.0-4 (source) into unstable (Thomas Goirand)
[2025-11-29] keystone 2:28.0.0-3 MIGRATED to testing (Debian testing watch)
[2025-11-26] Accepted keystone 2:28.0.0-3 (source) into unstable (Thomas Goirand)
[2025-11-19] Accepted keystone 2:27.0.0-3+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)

bugs [bug history graph]

all: 2
RC: 1
I&N: 0
M&W: 0
F&P: 1
patch: 0

links

homepage
lintian (0, 13)
buildd: logs, reproducibility
popcon
browse source code
other distros
security tracker
screenshots
l10n (83, 99)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2:29.0.0-0ubuntu2
patches for 2:29.0.0-0ubuntu2