Quick answers
- Is CVE-2013-4497 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2013-4497 being exploited in the wild.
- How severe is CVE-2013-4497?
- Informational severity, published 6 July 2026.
- Which products and versions are affected?
- OpenStack Compute Nova Folsom, Grizzly, and Havana before 2013.2; nova (PyPI) ECOSYSTEM:introduced=0,fixed=12.0.0a0.
- Is there a fix for CVE-2013-4497?
- Yes. nova (PyPI): upgrade to 12.0.0a0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2013-4497 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2013-4497?
- Check whether you run OpenStack Compute Nova or nova (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nova (PyPI): upgrade to 12.0.0a0 or later
pip install "nova>=12.0.0a0"
Technical details
The XenAPI backend in OpenStack Nova fails to properly reapply security group firewall rules during image resize operations and live migration. The root cause is that security group rules are not reapplied when instances are migrated to a new hypervisor or resized. An unauthenticated or authenticated remote attacker can exploit this by migrating or resizing an instance to bypass intended network access controls. The vulnerability affects Folsom, Grizzly, and Havana releases prior to 2013.2. Patches were applied to reapply firewall rules during finish_migrate and resize operations.
Affected products
- OpenStack Compute Nova Folsom, Grizzly, and Havana before 2013.2
Identifiers
- CVE-2013-4497
- GHSA-27q4-38qf-m25h
- PYSEC-2026-859
Timeline
- 2013-11-05: disclosed
- 2013.2: patched