How severe is CVE-2012-5625?

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

Which packages are affected by CVE-2012-5625?

CVE-2012-5625 affects the following packages: nova (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2012-5625?

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

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

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

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

CVE-2012-5625 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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-5625?

CVE-2012-5625 is classified as CWE-212 (CWE-212), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2012-5625 was published on May 17, 2022 and was last updated on June 8, 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-5625 — nova

Fix: openstack/nova@9d2ea97

CVE-2012-5625 is a CWE-212 vulnerability in nova. A fix is available for nova — see the affected versions and patch details below.

OpenStack Nova Information leak in libvirt LVM-backed instances

Also known asPYSEC-2012-42

Published

May 17, 2022

Updated

Jun 8, 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.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍nova

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 Compute (Nova) Folsom before 2012.2.2 and Grizzly, when using libvirt and LVM backed instances, does not properly clear physical volume (PV) content when reallocating for instances, which allows attackers to obtain sensitive information by reading the memory of the previous logical volume (LV).

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 2 configurations

Application

folsomopenstack

1 version

2012.2

Application

grizzlyopenstack

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nova to 12.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-5625 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2012-5625 (CC BY 4.0)

Product	Fixed in	Advisory
OpenStack Folsom for RHEL 6	`openstack-nova-0:2012.2.2-8.el6ost`	RHSA-2013:0208

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-5625 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works