How severe is CVE-2026-49299?

No CVSS score has been assigned to CVE-2026-49299 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-49299?

CVE-2026-49299 affects the following packages: neutron (PyPI), neutron (PyPI), neutron (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-49299?

Update neutron to 28.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49299 is resolved across your whole dependency graph.

How do I detect CVE-2026-49299 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neutron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-49299 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-49299 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-49299 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-49299?

CVE-2026-49299 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-49299?

CVE-2026-49299 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-49299 published, and has it been updated?

CVE-2026-49299 was published on May 28, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-49299 — neutron

CVE-2026-49299 is a CWE-863 vulnerability in neutron. A fix is available for neutron — see the affected versions and patch details below.

OpenStack Neutron has an Incorrect Authorization issue

Also known asGHSA-xv24-hxh9-2hh9PYSEC-2026-2678

Published

May 28, 2026

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-49299.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐍neutron🐍neutron🐍neutron

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`neutron`	≥ 28.0.0&&< 28.0.1	28.0.1`pip install --upgrade 'neutron==28.0.1'`
🐍PyPI	`neutron`	≥ 27.0.0&&< 27.0.3	27.0.3`pip install --upgrade 'neutron==27.0.3'`
🐍PyPI	`neutron`	≥ 26.0.0&&< 26.0.4	26.0.4`pip install --upgrade 'neutron==26.0.4'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neutron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neutron to 28.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49299 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This Moderate impact flaw in OpenStack Neutron, as shipped in Red Hat OpenStack Platform, allows a project reader to bypass policy restrictions. Due to a mismatch in policy enforcement for single-tag write operations, an authenticated attacker with project reader privileges can create and update tags on resources…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-49299 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-49299 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works