How severe is CVE-2012-4413?

No CVSS score has been assigned to CVE-2012-4413 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-4413?

CVE-2012-4413 affects the following packages: keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2012-4413?

Update keystone to 2012.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-4413 is resolved across your whole dependency graph.

How do I detect CVE-2012-4413 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-4413 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2012-4413 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-4413 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-4413?

CVE-2012-4413 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-4413?

CVE-2012-4413 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-4413 published, and has it been updated?

CVE-2012-4413 was published on September 18, 2012 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2012-4413 — keystone

Fix: openstack/keystone@58ac669

CVE-2012-4413 is a CWE-264 vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

OpenStack Keystone does not invalidate existing tokens when granting or revoking roles

Also known asGHSA-mrxv-65rv-6hxqPYSEC-2026-833

Published

Sep 18, 2012

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍keystone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

OpenStack Keystone before 2012.1.3 does not invalidate existing tokens when granting or revoking roles, which allows remote authenticated users to retain the privileges of the revoked roles.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	all versions	2012.1.3`pip install --upgrade 'keystone==2012.1.3'`

Affected Products

1 product · 1 configurations

Application

keystoneopenstack

1 version

2012.1.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keystone to 2012.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-4413 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
OpenStack Essex for RHEL 6	`openstack-keystone-0:2012.1.2-4.el6`	RHSA-2012:1378

Frequently Asked Questions

OpenStack Keystone before 2012.1.3 does not invalidate existing tokens when granting or revoking roles, which allows remote authenticated users to retain the privileges of the revoked roles.

O3 Security · Impact-Aware SCA

Is CVE-2012-4413 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works