How severe is GHSA-xv24-hxh9-2hh9?

No CVSS score has been assigned to GHSA-xv24-hxh9-2hh9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xv24-hxh9-2hh9?

GHSA-xv24-hxh9-2hh9 affects the following packages: neutron (PyPI), neutron (PyPI), neutron (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xv24-hxh9-2hh9?

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

How do I detect GHSA-xv24-hxh9-2hh9 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neutron. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xv24-hxh9-2hh9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-xv24-hxh9-2hh9?

O3 pinpoints whether GHSA-xv24-hxh9-2hh9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xv24-hxh9-2hh9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xv24-hxh9-2hh9 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 GHSA-xv24-hxh9-2hh9?

GHSA-xv24-hxh9-2hh9 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th 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 GHSA-xv24-hxh9-2hh9?

GHSA-xv24-hxh9-2hh9 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 GHSA-xv24-hxh9-2hh9 published, and has it been updated?

GHSA-xv24-hxh9-2hh9 was published on May 29, 2026 and was last updated on July 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xv24-hxh9-2hh9: OpenStack Neutron has an Incorrect Authori…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk21th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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
🐍PyPI	`neutron`	≥ 27.0.0&&< 27.0.3	27.0.3
🐍PyPI	`neutron`	≥ 26.0.0&&< 26.0.4	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update neutron to 28.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xv24-hxh9-2hh9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xv24-hxh9-2hh9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xv24-hxh9-2hh9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-xv24-hxh9-2hh9 in your dependencies?

O3 detects GHSA-xv24-hxh9-2hh9 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-xv24-hxh9-2hh9