VulnerabilityPublished 25 Nov 2024Updated 27 Oct 2026

CVE-2024-53916: In OpenStack Neutron before 25.0.1, neutron/extensions/tagging.py can use an incorrect ID during

Affects neutronSource GCVE Database

Authoritative record:CVE-2024-53916· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 24.04 LTSneutron`pkg:deb/ubuntu/neutron?arch=source&distro=noble`Other threats	Affected 2:23.0.0-0ubuntu1 – 2:24.2.2-0ubuntu0.24.04.1 9 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OpenStack Neutron to version 25.0.1 or later, or apply the corresponding patches for versions 23.2.1 and 24.0.2 or later. These versions include the fix that enforces proper policy checks on network tag modifications. No other mitigations are indicated by the vendor advisory.

Description

CVE-2024-53916 is a vulnerability in OpenStack Neutron before version 25.0.1 where the tagging.py module improperly enforces policy checks. This flaw allows an unprivileged tenant to add or clear tags on network objects that belong to other tenants without proper authorization. The issue affects versions 23 before 23.2.1, 24 before 24.0.2, and 25 before 25.0.1.

Impact

An unprivileged tenant can modify tags on network objects belonging to other tenants without proper authorization. While this does not directly compromise confidentiality or availability, it impacts the integrity of network metadata and could lead to misconfiguration or unauthorized network management actions. The CVSS 3.1 base score is 7.5 (high severity), reflecting the ease of exploitation (network vector, no privileges required, no user interaction) and the impact on integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 03:26 UTC

Technical details

References

Community reviews

Related threats