Linux ·
Ubuntu · Package update · June 24, 2026
Ubuntu · Package update · June 24, 2026python3-keystone 2:28.0.0-0ubuntu1.3: python3-keystone 2:28.0.0-0ubuntu1.3 for Ubuntu 25.10 (questing)
python3-keystone 2:28.0.0-0ubuntu1.3, released June 24, 2026, fixes 7 CVEs in python3-keystone. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.
HighUnsupported product
CVEs closed
7
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0047
40th percentile
Priority of the 7 CVEs
Patch now 0
Urgent 0
High 6
Routine 1
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| python3-keystone | Ubuntu 25.10 (questing) | 2:28.0.0-0ubuntu1.3 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-43001 | keystone: An issue was discovered in OpenStack Keystone before 29.0.2 | 8.0 | 0.0047 | None reported |
| High | CVE-2026-40683 | keystone: In OpenStack Keystone before 28.0.1, the LDAP identity backend does not convert the user enabled attribute to a boole... | 7.7 | 0.0034 | None reported |
| High | CVE-2026-42999 | keystone: An issue was discovered in OpenStack Keystone before 29.0.2 | 8.8 | 0.0033 | None reported |
| High | CVE-2026-43000 | keystone: An issue was discovered in OpenStack Keystone before 29.0.2 | 8.8 | 0.0033 | None reported |
| High | CVE-2026-42998 | keystone: An issue was discovered in OpenStack Keystone before 29.0.2 | 8.8 | 0.0030 | None reported |
| High | CVE-2026-44394 | keystone: An issue was discovered in OpenStack Keystone before 29.0.2 | 8.1 | 0.0025 | None reported |
| Routine | CVE-2026-33551 | keystone: An issue was discovered in OpenStack Keystone 14 through 26 before 26.1.1, 27.0.0, 28.0.0, and 29.0.0 | 5.3 | 0.0023 | None reported |
Showing 1 to 7 of 7
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.