keystone - Debian Package Tracker

general

source: keystone (main)
version: 2:29.0.2-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.2-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]
2:29.0.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:29.0.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

keystone
keystone-doc
python3-keystone

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

https://salsa.debian.org/api/v4/projects/openstack-team%2Fservices%2Fkeystone API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.

Created: 2026-08-27 Last update: 2026-08-28 10:33

Marked for autoremoval on 18 September due to httpcore, ipywidgets, python-libcst, python-repoze.who, towncrier: #1143321, #1143428, #1143694, #1144575, #1144936 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-libcst, python-repoze.who, towncrier, affected by #1143321, #1143428, #1143694, #1144575, #1144936. You should try to prevent the removal by fixing these RC bugs.

Created: 2026-08-01 Last update: 2026-08-28 10:32

3 security issues in trixie high

There are 3 open security issues in trixie.

3 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-80183: In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain ID as scope.project.id with include_subtree to the GET /v3/role_assignments endpoint. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. With include_names, the response discloses the names and home-domain IDs of every user, group, project, and role involved. The literal "default" domain ID works against any deployment created with keystone-manage bootstrap. An attacker can harvest domain IDs from the response and repeat the query to map role assignments across the entire cloud. This is caused by misuse of "None" in list_role_assignments_for_tree.
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-28 01:00

3 security issues in forky high

There are 3 open security issues in forky.

3 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-80183: In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain ID as scope.project.id with include_subtree to the GET /v3/role_assignments endpoint. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. With include_names, the response discloses the names and home-domain IDs of every user, group, project, and role involved. The literal "default" domain ID works against any deployment created with keystone-manage bootstrap. An attacker can harvest domain IDs from the response and repeat the query to map role assignments across the entire cloud. This is caused by misuse of "None" in list_role_assignments_for_tree.
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-28 01:00

4 security issues in bullseye high

There are 4 open security issues in bullseye.

3 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-80183: In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain ID as scope.project.id with include_subtree to the GET /v3/role_assignments endpoint. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. With include_names, the response discloses the names and home-domain IDs of every user, group, project, and role involved. The literal "default" domain ID works against any deployment created with keystone-manage bootstrap. An attacker can harvest domain IDs from the response and repeat the query to map role assignments across the entire cloud. This is caused by misuse of "None" in list_role_assignments_for_tree.
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-28 01:00

4 security issues in bookworm high

There are 4 open security issues in bookworm.

3 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-80183: In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain ID as scope.project.id with include_subtree to the GET /v3/role_assignments endpoint. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. With include_names, the response discloses the names and home-domain IDs of every user, group, project, and role involved. The literal "default" domain ID works against any deployment created with keystone-manage bootstrap. An attacker can harvest domain IDs from the response and repeat the query to map role assignments across the entire cloud. This is caused by misuse of "None" in list_role_assignments_for_tree.
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-28 01:00

lintian reports 20 warnings normal

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

Created: 2026-08-28 Last update: 2026-08-28 00:18

debian/patches: 6 patches to forward upstream low

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

6 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-08-28 07:00

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-08-28 00:21

testing migrations

excuses:
- Migration status for keystone (2:29.0.1-2 to 2:29.0.2-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for keystone/2:29.0.2-2: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Updating keystone will fix bugs in testing: #1145816
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keystone.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[rss feed]

[2026-08-27] Accepted keystone 2:29.0.2-2 (source) into unstable (Thomas Goirand)
[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)

bugs [bug history graph]

all: 0

links

homepage
lintian (0, 20)
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