CVE-2024-53916High· 7.5▾ TwilightOpenStack Neutron can use an incorrect ID during policy enforcement
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.7%
0.7% → 0.7%
In OpenStack Neutron before 25.0.1, neutron/extensions/tagging.py can use an incorrect ID during policy enforcement. It does not apply the proper policy check for changing network tags. An unprivileged tenant is able to change (add and clear) tags on network objects that do not belong to the tenant, and this action is not subjected to the proper policy authorization check. This affects 23 before 23.2.1, 24 before 24.0.2, and 25 before 25.0.1.
neutron >= 23.0.0, < 23.2.1neutron >= 24.0.0, < 24.0.2neutron >= 25.0.0, < 25.0.1Upgrade to a patched release:
neutron 23.2.1neutron 24.0.2neutron 25.0.1Connected by shared product, vendor, weakness, or advisory.
CVE-2026-50266Low· 2.2OpenStack Neutron: Neutron port RBAC policy bypass allows project managers to set trusted device owners on shared networks
CVE-2026-49299MediumOpenStack Neutron has an Incorrect Authorization issue
CVE-2022-3277Medium· 6.5openstack-neutron uncontrolled resource consumption flaw
CVE-2016-5362High· 8.2OpenStack Neutron allows remote attackers to bypass an intended DHCP-spoofing protection mechanism
CVE-2015-5240LowOpenStack Neutron Race condition vulnerability
CVE-2016-5363High· 8.2OpenStack Neutron Intended MAC-spoofing protection mechanism bypass