PYSEC-2026-867
Vulnerability from pysec - Published: 2026-07-06 08:03 - Updated: 2026-07-07 11:30OpenStack Compute (Nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) do not properly apply security group changes, which allows remote attackers to bypass intended restriction by leveraging an instance that was running when the change was made.
| Name | purl | nova | pkg:pypi/nova |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "nova",
"purl": "pkg:pypi/nova"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2014.2.4"
},
{
"introduced": "2015.1.0"
},
{
"fixed": "2015.1.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"15.1.5",
"16.1.6",
"16.1.7",
"16.1.8",
"17.0.10",
"17.0.11",
"17.0.12",
"17.0.13",
"17.0.7",
"17.0.8",
"17.0.9",
"18.0.2",
"18.0.3",
"18.1.0",
"18.2.0",
"18.2.1",
"18.2.2",
"18.2.3",
"18.3.0",
"19.0.0",
"19.0.0.0rc1",
"19.0.0.0rc2",
"19.0.1",
"19.0.2",
"19.0.3",
"19.1.0",
"19.2.0",
"19.3.0",
"19.3.1",
"19.3.2",
"20.0.0",
"20.0.0.0rc1",
"20.0.0.0rc2",
"20.0.1",
"20.1.0",
"20.1.1",
"20.2.0",
"20.3.0",
"20.4.0",
"20.4.1",
"20.5.0",
"20.6.0",
"20.6.1",
"21.0.0",
"21.0.0.0rc1",
"21.0.0.0rc2",
"21.1.0",
"21.1.1",
"21.1.2",
"21.2.0",
"21.2.1",
"21.2.2",
"21.2.3",
"21.2.4",
"22.0.0",
"22.0.0.0rc1",
"22.0.1",
"22.1.0",
"22.2.0",
"22.2.1",
"22.2.2",
"22.3.0",
"22.4.0",
"23.0.0",
"23.0.0.0rc1",
"23.0.0.0rc2",
"23.0.1",
"23.0.2",
"23.1.0",
"23.2.0",
"23.2.1",
"23.2.2",
"24.0.0",
"24.0.0.0rc1",
"24.0.0.0rc2",
"24.1.0",
"24.1.1",
"24.2.0",
"24.2.1",
"25.0.0",
"25.0.0.0rc1",
"25.0.1",
"25.1.0",
"25.1.1",
"25.2.0",
"25.2.1",
"25.3.0",
"26.0.0",
"26.0.0.0rc1",
"26.0.0.0rc2",
"26.1.0",
"26.1.1",
"26.2.0",
"26.2.1",
"26.2.2",
"26.3.0",
"27.0.0",
"27.0.0.0rc1",
"27.1.0",
"27.2.0",
"27.3.0",
"27.4.0",
"27.5.0",
"27.5.1",
"28.0.0",
"28.0.0.0rc1",
"28.0.1",
"28.1.0",
"28.2.0",
"28.3.0",
"28.3.1",
"29.0.0",
"29.0.0.0rc1",
"29.0.1",
"29.0.2",
"29.1.0",
"29.2.0",
"29.2.1",
"29.2.2",
"29.3.0",
"29.4.0",
"30.0.0",
"30.0.0.0rc1",
"30.1.0",
"30.2.0",
"30.2.1",
"30.3.0",
"31.0.0",
"31.0.0.0rc1",
"31.0.1",
"31.1.0",
"31.2.0",
"31.3.0",
"31.3.1",
"32.0.0",
"32.0.0.0rc1",
"32.1.0",
"32.2.0",
"32.2.1",
"33.0.0",
"33.0.0.0rc1",
"33.0.1",
"33.0.2"
]
}
],
"aliases": [
"CVE-2015-7713",
"GHSA-67rh-9p29-vrxr"
],
"details": "OpenStack Compute (Nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) do not properly apply security group changes, which allows remote attackers to bypass intended restriction by leveraging an instance that was running when the change was made.",
"id": "PYSEC-2026-867",
"modified": "2026-07-07T11:30:49.678192Z",
"published": "2026-07-06T08:03:22.469140Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-7713"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2015:2673"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2015:2684"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2016:0013"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2016:0017"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2015-7713"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/nova/+bug/1491307"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/nova/+bug/1492961"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1269119"
},
{
"type": "PACKAGE",
"url": "https://opendev.org/openstack/nova"
},
{
"type": "WEB",
"url": "https://security.openstack.org/ossa/OSSA-2015-021.html"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20200228024902/http://www.securityfocus.com/bid/76960"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2015-2684.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/76960"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/nova"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-67rh-9p29-vrxr"
}
],
"summary": "OpenStack Compute (Nova) allows remote attackers to bypass intended restriction"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.