# CVE-2026-49299: OpenStack Neutron has an Incorrect Authorization issue

> A policy mismatch in OpenStack Neutron allows project readers to modify tags on resources, bypassing intended authorization restrictions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-49299, GHSA-xv24-hxh9-2hh9, PYSEC-2026-2678, UBUNTU-CVE-2026-49299

## What is CVE-2026-49299?

CVE-2026-49299 is a medium-severity missing authorization vulnerability in OpenStack Neutron, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenStack Neutron before 28.0.1, the tagging controller enforces plural policy action names on single-tag write operations while the defined policy rules use singular names. The mismatched names evaluate as allowed under the default policy, permitting a project reader to create and update tags on same-project resources. Deployments running Neutron 26.0.0 or later are affected.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-49299?

7 open source packages ship an affected version, including neutron.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `neutron` | PyPI | From 26.0.0 | 26.0.4, 27.0.3, 28.0.1 |
| `neutron` | PyPI | From 26.0.0 | 26.0.4 |
| `neutron` | PyPI | From 26.0.0 | 26.0.4 |
| `neutron` | PyPI | From 27.0.0 | 27.0.3 |
| `neutron` | PyPI | From 27.0.0 | 27.0.3 |
| `neutron` | PyPI | From 28.0.0 | 28.0.1 |
| `neutron` | PyPI | From 28.0.0 | 28.0.1 |

## How do I fix CVE-2026-49299?

Upgrade neutron to a fixed version for your release line: 26.0.4, 27.0.3 or 28.0.1.

## Is CVE-2026-49299 being exploited?

There is no known exploitation of CVE-2026-49299 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49299 and fix it if it is affected.

What it is: CVE-2026-49299 is a medium-severity missing authorization vulnerability in OpenStack Neutron, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49299 in the wild and no public exploit code.

Affected packages and fixed versions:
- neutron (PyPI): affected from 26.0.0; fixed in 26.0.4, 27.0.3, 28.0.1
- neutron (PyPI): affected from 26.0.0; fixed in 26.0.4
- neutron (PyPI): affected from 26.0.0; fixed in 26.0.4
- neutron (PyPI): affected from 27.0.0; fixed in 27.0.3
- neutron (PyPI): affected from 27.0.0; fixed in 27.0.3
- neutron (PyPI): affected from 28.0.0; fixed in 28.0.1
- neutron (PyPI): affected from 28.0.0; fixed in 28.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49299/ (Markdown: https://insights.sbomify.com/CVE-2026-49299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49299
- OSV: https://osv.dev/vulnerability/CVE-2026-49299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49299/
Summaries are generated and may contain mistakes; the official description above is the record.