CVE-2026-44394: An issue was discovered in OpenStack Keystone before 29.0.2.
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: OpenStack Keystone 27.0.2, 28.0.2, 29.0.2.
- Severity is disputed: the assigning authority (CNA) scores it 6.0, NVD 8.1.
Low priority for now. Upgrade to OpenStack Keystone 27.0.2, 28.0.2, 29.0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 28, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-863
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.1
- CNA · mitre
- 6.0
- 2.1 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openstack | keystone | cpe:2.3:a:openstack:keystone |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openstack keystone14.0.0 and later · before 27.0.2
- openstack keystone28.0.0 and later · before 28.0.2
- openstack keystone29.0.0 and later · before 29.0.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.
OpenStack Keystone
- 14.0.0 and later · before 27.0.2affected · semver
- 28.0.0 and later · before 28.0.2affected · semver
- 29.0.0 and later · before 29.0.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | keystone | before 2:22.0.2-0+deb12u3 | 2:22.0.2-0+deb12u3 |
| Debian:13 | keystone | before 2:27.0.0-3+deb13u4 | 2:27.0.0-3+deb13u4 |
| Debian:14 | keystone | before 2:29.0.1-2 | 2:29.0.1-2 |
| PyPI | keystone | from 14.0.0 · before 27.0.2 | 27.0.2 |
| PyPI | keystone | from 28.0.0 · before 28.0.2 | 28.0.2 |
| PyPI | keystone | from 29.0.0 · before 29.0.2 | 29.0.2 |
Same product
openstack: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-12691An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.36Monitor
- CVE-2020-12690An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.36Monitor
- CVE-2019-19687OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-42999May 28, 2026 · An issue was discovered in OpenStack Keystone before 29.0.2.35Monitor
- ← EarlierCVE-2026-43000May 28, 2026 · An issue was discovered in OpenStack Keystone before 29.0.2.35Monitor
- Later →CVE-2026-80182Aug 25, 2026 · In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenStack Keystone | 27.0.2 | Vendor (CNA) |
| OpenStack Keystone | 28.0.2 | Vendor (CNA) |
| OpenStack Keystone | 29.0.2 | Vendor (CNA) |
| debian:keystone | 2:22.0.2-0+deb12u3 · Debian:12 | Package registry (OSV) |
| PyPI:keystone | 27.0.2 | Package registry (OSV) |
| PyPI:keystone | 28.0.2 | Package registry (OSV) |
| PyPI:keystone | 29.0.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-429980 days apartAn issue was discovered in OpenStack Keystone before 29.0.2.35Monitor
- CVE-2026-429990 days apartAn issue was discovered in OpenStack Keystone before 29.0.2.35Monitor
- CVE-2026-430000 days apartAn issue was discovered in OpenStack Keystone before 29.0.2.35Monitor
- CVE-2026-4300127 days apartAn issue was discovered in OpenStack Keystone before 29.0.2.32Monitor
- CVE-2026-8018289 days apartIn OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could…30Monitor
- CVE-2026-8018489 days apartIn OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application…30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.