OpenStack Identity Keystone is vulnerable to Block delegation escalation of privilege

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2014-3476: 2.33% estimated exploitation activity in the next 30 days; percentile 83.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

OpenStack Identity (Keystone) before 2013.2.4, 2014.1 before 2014.1.2, and Juno before Juno-2 does not properly handle chained delegation, which allows remote authenticated users to gain privileges by leveraging a (1) trust or (2) OAuth token with impersonation enabled to create a new token with additional roles.

Published by the source

13 May 2022, 01:26 UTC

Last modified by the source

6 Jul 2026, 08:11 UTC

Source last checked

26 Oct 2026, 13:13 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-274v-r947-v34r

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-274v-r947-v34r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2014-3476

Advisory: OpenStack Identity Keystone is vulnerable to Block delegation escalation of privilege
IDs: CVE-2014-3476, GHSA-274v-r947-v34r
Record: https://patchnext.com/advisories/cve-2014-3476 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keystone 8.0.0a0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI keystone: affected < 8.0.0a0; fixed in 8.0.0a0

## Suggested inspection (read-only)
- `python -m pip show keystone`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on keystone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-274v-r947-v34r (OSV record GHSA-274v-r947-v34r lists affected ranges: PyPI keystone >=0 <8.0.0a0 (fixed))
- Verified: https://github.com/advisories/GHSA-274v-r947-v34r (GitHub-reviewed advisory GHSA-274v-r947-v34r lists affected ranges: PyPI keystone >=0 <8.0.0a0)

Commands are suggestions: review each one before running it.