How severe is CVE-2016-2140?

CVE-2016-2140 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-2140?

CVE-2016-2140 affects the following packages: nova (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2016-2140?

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

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

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

CVE-2016-2140 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th 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-2016-2140?

CVE-2016-2140 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-2140 published, and has it been updated?

CVE-2016-2140 was published on April 12, 2016 and was last updated on October 24, 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-2016-2140 — nova

MEDIUMFix: openstack/nova@0b19418

CVE-2016-2140 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in nova. A fix is available for nova — see the affected versions and patch details below.

OpenStack Nova host data access through resize/migration

Also known asGHSA-49jv-37hm-6gfpPYSEC-2026-864

Published

Apr 12, 2016

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% 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

🐍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

The libvirt driver in OpenStack Compute (Nova) before 2015.1.4 (kilo) and 12.0.x before 12.0.3 (liberty), when using raw storage and use_cow_images is set to false, allows remote authenticated users to read arbitrary files via a crafted qcow2 header in an ephemeral or root disk.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nova`	≥ 12.0.0&&< 12.0.3	12.0.3`pip install --upgrade 'nova==12.0.3'`

Affected Products

1 product · 2 configurations

Application

novaopenstack

≥ 2015.1.0 && < 2015.1.4

range

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.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-2140 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 HatImportant

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-nova-0:2014.1.5-29.el6ost`	RHSA-2016:0366
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-nova-0:2014.1.5-29.el7ost`	RHSA-2016:0365
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-nova-0:2014.2.3-54.2.el7ost`	RHSA-2016:0364
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7	`openstack-nova-0:2015.1.2-18.2.el7ost`	RHSA-2016:0363

UbuntuMEDIUM

USN-3449-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-2140 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works