How severe is CVE-2014-5252?

CVE-2014-5252 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-5252?

CVE-2014-5252 affects the following packages: keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-5252?

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

How do I detect CVE-2014-5252 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-2014-5252 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-2014-5252 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-5252 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-2014-5252?

CVE-2014-5252 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 75th 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-2014-5252?

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

When was CVE-2014-5252 published, and has it been updated?

CVE-2014-5252 was published on August 25, 2014 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

Not in CISA KEV

MEDIUM severity

CVE-2014-5252 — keystone

MEDIUMFix: openstack/keystone@556fb86

CVE-2014-5252 is a medium-severity (CVSS 6.5) CWE-255 vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

OpenStack Identity (Keystone) UUID v2 tokens does not expire with revocation events

Also known asGHSA-v8fq-gq9j-3v7hPYSEC-2014-108

Published

Aug 25, 2014

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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

The V3 API in OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 updates the issued_at value for UUID v2 tokens, which allows remote authenticated users to bypass the token expiration and retain access via a verification (1) GET or (2) HEAD request to v3/auth/tokens/.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 5 configurations

ubuntu linuxcanonical

1 version

14.04

Application

keystoneopenstack

4 versions

2014.12014.1.2juno-1juno-2

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 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-5252 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 HatLow

This issue does not affected openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 4.0.

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-keystone-0:2014.1.2.1-2.el6ost`	RHSA-2014:1122
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-keystone-0:2014.1.2.1-1.el7ost`	RHSA-2014:1121

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-5252 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-255CWE-255

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

keystone

3.5/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Aug 25, 2014

Last updated

Apr 10, 2026

Identifiers

CVE-2014-5252

GHSA-v8fq-gq9j-3v7h

PYSEC-2014-108

References

Advisoryrhn.redhat.com · RHSA 2014 1121 Advisoryrhn.redhat.com · RHSA 2014 1122 Advisoryubuntu.com · USN 2324 1 Advisorynvd.nist.gov · CVE 2014 5252 Webopenwall.com Webbugs.launchpad.net Webgithub.com · 556fb860311675fc437585651e4602b2908451eb Webgithub.com · a4c73e4382cb062aa9f30fe1960d5014d3c49cc2 Webgithub.com · bdb88c662ac2035f9b0d8a229a5db5f60f5f16ae Webgithub.com · PYSEC 2014 108.yaml Packagegithub.com · keystone

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting keystone are rated as high or higher (top: high).

CVE-2026-42999CVE-2026-42998CVE-2026-43000CVE-2026-44394CVE-2026-43001CVE-2026-40683CVE-2026-33551CVE-2025-65073

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026

CVE-2014-5252 — keystone

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2014-5252 in your dependencies?