NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2020-17376 — nova

HIGHFix: openstack/nova@1bb8ee9

CVE-2020-17376 is a high-severity (CVSS 8.3) XML External Entity (XXE) vulnerability in nova. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for nova — see the affected versions and patch details below.

OpenStack Nova Live migration fails to update persistent domain XML

Also known asGHSA-c7w7-9c85-4qxvPYSEC-2020-243
Published
Updated
Affected
3 pkgs
Patched
2 / 3
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk+0.03%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.00%0.75%1.51%2.26%0.4%1.8%May 26Sep 26Nov 26

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

3 pkgs affected
🐍nova🐍nova🐍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

An issue was discovered in Guest.migrate in virt/libvirt/guest.py in OpenStack Nova before 19.3.1, 20.x before 20.3.1, and 21.0.0. By performing a soft reboot of an instance that has previously undergone live migration, a user may gain access to destination host devices that share the same paths as host devices previously referenced by the virtual machine on the source host. This can include block devices that map to different Cinder volumes at the destination than at the source. Only deployments allowing host-based connections (for instance, root and ephemeral devices) are affected.

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPInovaall versions19.3.1pip install --upgrade 'nova==19.3.1'
🐍PyPInova≥ 20.0.0&&< 20.3.120.3.1pip install --upgrade 'nova==20.3.1'
🐍PyPInovaall versionsNo fix

Affected Products

1 product · 3 configurations
Application
novaopenstack
≥ 20.0.0 && < 20.3.1
1 version
21.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in Guest.migrate in virt/libvirt/guest.py in Ope…

launchpad.netNVDSep 2020

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

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

  3. 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 HatImportant

Red Hat OpenStack Platform 10 was initially marked as affected, however it has since been discovered that the flaw is actually not present in this version. For this reason, the update in RHSA-2020:3711 can be either applied or ignored for RHOSP 10.

Workaround published by Red Hat
Public clouds using non-default configurations (allowing untrusted users to initiate live migrations) face significant additional risk. If it is not possible to immediately apply patches, a temporary policy change is recommended: disable soft reboots by setting wait_soft_reboot_seconds to zero. This effectively forces any soft reboots to instead be overridden as a hard reboot. Find more information in Nova's documentation https://docs.openstack.org/nova/ussuri/configuration/config.html Deployments which use unique device paths for each cinder volume face an extremely low risk of being affected by this flaw.
Source: Red Hat security advisory for CVE-2020-17376 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat OpenStack Platform 10.0 (Newton)openstack-nova-1:14.1.0-65.el7ostRHSA-2020:3711
Red Hat OpenStack Platform 13.0 (Queens)openstack-nova-1:17.0.13-24.el7ostRHSA-2020:3708
Red Hat OpenStack Platform 15.0 (Stein)openstack-nova-1:19.1.0-0.20200207070459.bf9d9e5.el8ostRHSA-2020:3706
Red Hat OpenStack Platform 16.0 (Train)openstack-nova-1:20.1.2-0.20200401205215.28324e6.el8ostRHSA-2020:3704
Red Hat OpenStack Platform 16.1openstack-nova-1:20.3.1-0.20200626213436.38ee1f3.el8ostRHSA-2020:3702

Frequently Asked Questions

An issue was discovered in Guest.migrate in virt/libvirt/guest.py in OpenStack Nova before 19.3.1, 20.x before 20.3.1, and 21.0.0. By performing a soft reboot of an instance that has previously undergone live migration, a user may gain access to destination host devices that share the same paths as host devices previously referenced by the virtual machine on the source host. This can include block devices that map to different Cinder volumes at the destination than at the source. Only deployments allowing host-based connections (for instance, root and ephemeral devices) are affected.
O3 Security · Impact-Aware SCA

Is CVE-2020-17376 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-17376: nova — Fixed in 19.3.1