OpenStack Nova instance migration process does not stop when instance is deleted

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2015-3241: 3.48% estimated exploitation activity in the next 30 days; percentile 89.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

14 May 2022, 01:58 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

24 Oct 2026, 04:13 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3vx7-xff6-h2vx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2015-3241

Advisory: OpenStack Nova instance migration process does not stop when instance is deleted
IDs: CVE-2015-3241, GHSA-3vx7-xff6-h2vx
Record: https://patchnext.com/advisories/cve-2015-3241 (revision 1, source checked 24 Oct 2026, 04:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nova 112.0.0.0b3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nova: affected < 112.0.0.0b3; fixed in 112.0.0.0b3

## Suggested inspection (read-only)
- `python -m pip show nova`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nova.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3vx7-xff6-h2vx (OSV record GHSA-3vx7-xff6-h2vx lists affected ranges: PyPI nova >=0 <112.0.0.0b3 (fixed))

Commands are suggestions: review each one before running it.