Skip to content
Fencer Intel
high 7.5

CVE-2024-53916 json

OpenStack Neutron can use an incorrect ID during policy enforcement

published last yr. modified 4mo ago also GHSA-f27h-g923-68hw , PYSEC-2026-1693 , EUVD-2024-3352

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi neutron 23.2.1, 24.0.2, 25.0.1
  • neutron Debian 14, Debian 13 2:25.0.0-2

debian advisories DEBIAN-CVE-2024-53916

Is CVE-2024-53916 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-53916 updated cvss 5.3

openstack-neutron: tagging.py can use an incorrect ID during policy enforcement

  • Red Hat OpenStack Platform 16.2 python3-neutron, openstack-neutron, openstack-heat-api, openstack-heat-common, openstack-heat-engine, openstack-neutron-ml2, +9 more Red Hat OpenStack Platform 17.1 python3-neutron, openstack-neutron, openstack-heat-api, openstack-heat-common, openstack-heat-engine, openstack-neutron-ml2, +12 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.71% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi neutron
>=23.0.0, <23.2.1
>=24.0.0, <24.0.2
>=25.0.0, <25.0.1
23.2.1
24.0.2
25.0.1

Affected products

  • openstack neutron

Classification

Weakness
  • CWE-754 Improper Check for Unusual or Exceptional Conditions
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.