How severe is CVE-2012-3426?

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

Which packages are affected by CVE-2012-3426?

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

How do I fix CVE-2012-3426?

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

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2012-3426 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.

How does O3 Security protect against CVE-2012-3426?

O3 pinpoints whether CVE-2012-3426 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 2 known exploit references for CVE-2012-3426, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2012-3426?

CVE-2012-3426 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-3426 published, and has it been updated?

CVE-2012-3426 was published on July 31, 2012 and was last updated on April 10, 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

CVE-2012-3426

CVE-2012-3426 is a CWE-264 vulnerability in keystone. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2012-3426 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenStack Keystone token expiration issues

Also known asGHSA-xp97-6w7r-4cjc

Published

Jul 31, 2012

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Blast Radius

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.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	all versions	8.0.0a0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before F…

github.comNVDSep 2012

OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before F…

github.comNVDSep 2012

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update keystone to 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3426 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.
How O3 protects you
O3 pinpoints whether CVE-2012-3426 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2012-3426. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-3426 in your dependencies?

O3 detects CVE-2012-3426 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works