CVE-2026-50266VulnerabilityPublished 4 Jun 2026Updated 27 Oct 2026

In OpenStack Neutron before 28.0.1, a project manager can create or update a port on a shared network owned by another

Affects neutronSource GCVE Database

Mentioned vulnerabilities

CVE-2015-5240

Authoritative record:CVE-2026-50266· Low 2.2

Not known to be exploited · CVSS 2.2 Low.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score

2.2Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 4 Jun 2026
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 26.10neutron`pkg:deb/ubuntu/neutron?arch=source&distro=stonking`Other threats	Affected 2:28.0.0-0ubuntu1 – 2:29.0.0~rc1-0ubuntu1 5 affected builds	Fixed in–
Ubuntu 26.04 LTSneutron`pkg:deb/ubuntu/neutron?arch=source&distro=resolute`Other threats	Affected 2:27.0.0-0ubuntu1 – 2:28.0.2-0ubuntu1 7 affected builds	Fixed in–
Ubuntu 25.10neutron`pkg:deb/ubuntu/neutron?arch=source&distro=questing`Other threats	Affected 2:26.0.0-0ubuntu1 – 2:27.0.0~rc1-0ubuntu1 6 affected builds	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–
Ubuntu 22.04 LTSneutron`pkg:deb/ubuntu/neutron?arch=source&distro=jammy`Other threats	Affected 2:19.0.0-0ubuntu1 – 2:20.5.0-0ubuntu2.1 14 affected builds	Fixed in–
Ubuntu 20.04 LTSneutron`pkg:deb/ubuntu/neutron?arch=source&distro=focal`Other threats	Affected 2:15.0.0-0ubuntu1 – 2:16.4.2-0ubuntu6.4 36 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 28.0.1 or later where this vulnerability is fixed. Since this is a regression of a previously addressed issue, applying the official fix is necessary to restore proper RBAC enforcement. No other mitigation or workaround is indicated in the provided data.

Description

OpenStack Neutron versions before 28.0.1 contain a vulnerability where a project manager can create or update a port on a shared network owned by another project and assign a device_owner value starting with "network:". This occurs due to incorrect RBAC policies that include PROJECT_MANAGER without requiring network ownership. The flaw can allow bypassing of anti-spoofing and security group protections, enabling DHCP, MAC, or IP spoofing attacks on shared networks. This vulnerability is a regression of CVE-2015-5240.

Impact

The vulnerability allows a project manager to gain elevated network privileges on shared networks owned by other projects, potentially bypassing anti-spoofing and security group protections. This can enable spoofing attacks such as DHCP, MAC, or IP spoofing against other tenants sharing the network. The CVSS score of 2.2 (low severity) reflects that the impact is limited to integrity with no confidentiality or availability impact, and requires high privileges and network access.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats