How severe is GHSA-3vx7-xff6-h2vx?

No CVSS score has been assigned to GHSA-3vx7-xff6-h2vx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3vx7-xff6-h2vx?

GHSA-3vx7-xff6-h2vx affects the following packages: nova (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-3vx7-xff6-h2vx?

Update nova to 112.0.0.0b3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vx7-xff6-h2vx is resolved across your whole dependency graph.

How do I detect GHSA-3vx7-xff6-h2vx 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 GHSA-3vx7-xff6-h2vx if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-3vx7-xff6-h2vx actively exploited in the wild?

No public exploit code has been indexed for GHSA-3vx7-xff6-h2vx 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 GHSA-3vx7-xff6-h2vx?

GHSA-3vx7-xff6-h2vx has an EPSS (Exploit Prediction Scoring System) score of 3.5%, placing it in the 89th 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 GHSA-3vx7-xff6-h2vx?

GHSA-3vx7-xff6-h2vx is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3vx7-xff6-h2vx published, and has it been updated?

GHSA-3vx7-xff6-h2vx was published on May 14, 2022 and was last updated on September 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.

OpenStack Nova instance migration process does not…

EPSS Exploitation Probability

via FIRST.org ↗

3.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% 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) 2015.1 through 2015.1.1, 2014.2.3, and earlier does not stop the migration process when the instance is deleted, which allows remote authenticated users to cause a denial of service (disk, network, and other resource consumption) by resizing and then deleting an instance.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 2 configurations

Application

novaopenstack

≥ 2015.1.0 && ≤ 2015.1.1

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 112.0.0.0b3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vx7-xff6-h2vx is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-nova-0:2014.1.5-3.el6ost`	RHSA-2015:1898
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7	`openstack-nova-0:2015.1.0-18.el7ost`	RHSA-2015:1723

Frequently Asked Questions

OpenStack Compute (nova) 2015.1 through 2015.1.1, 2014.2.3, and earlier does not stop the migration process when the instance is deleted, which allows remote authenticated users to cause a denial of service (disk, network, and other resource consumption) by resizing and then deleting an instance.

O3 Security · Impact-Aware SCA

Is GHSA-3vx7-xff6-h2vx in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

OpenStack Nova instance migration process does not stop when instance is deletedGHSA-3vx7-xff6-h2vx