# OpenStack Neutron: Neutron port RBAC policy bypass allows project managers to set trusted device owners on shared networks

Advisory record · `GHSA-qmc5-gv6v-8p22`

- **Identifiers:** `GHSA-qmc5-gv6v-8p22` · `CVE-2026-50266` · `PYSEC-2026-3491`
- **State:** Confirmed
- **Severity:** CVSS 2.2 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 4 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `neutron` (PyPI): affected `<28.0.1`; fixed in `28.0.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> OpenStack Neutron versions before 28.0.1 are affected. A project manager can create or update a port on a shared network owned by another project and set its device_owner to a value beginning with "network:", which bypasses default port RBAC policy. The attacker can then gain trusted network-service port behavior and, depending on backend and deployment, spoof DHCP, MAC, or IP addresses against other tenants on that network. Upgrade to Neutron 28.0.1.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.2 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qmc5-gv6v-8p22)

## Sources

- [GitHub Advisory Database: GHSA-qmc5-gv6v-8p22](https://github.com/advisories/GHSA-qmc5-gv6v-8p22)
- [OSV: GHSA-qmc5-gv6v-8p22](https://osv.dev/vulnerability/GHSA-qmc5-gv6v-8p22)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-50266>
- <https://bugs.launchpad.net/neutron/+bug/2152115>
- <https://github.com/openstack/neutron>
- <https://launchpad.net/bugs/2152115>
- <https://review.opendev.org/990273>
- <https://review.opendev.org/990353>
- <https://review.opendev.org/990356>
- <https://www.openwall.com/lists/oss-security/2026/06/04/6>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qmc5-gv6v-8p22>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qmc5-gv6v-8p22/>. Everything for agents: <https://agentprime.io/llms.txt>.
