How severe is GHSA-46r8-9cj7-pw6g?

No CVSS score has been assigned to GHSA-46r8-9cj7-pw6g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-46r8-9cj7-pw6g?

GHSA-46r8-9cj7-pw6g affects the following packages: nova (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-46r8-9cj7-pw6g?

Update nova to 12.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-46r8-9cj7-pw6g is resolved across your whole dependency graph.

How do I detect GHSA-46r8-9cj7-pw6g in my PyPI dependencies?

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

How do I mitigate GHSA-46r8-9cj7-pw6g 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-46r8-9cj7-pw6g?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-46r8-9cj7-pw6g can be triaged on real exposure rather than presence alone.

Is GHSA-46r8-9cj7-pw6g actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-46r8-9cj7-pw6g, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-46r8-9cj7-pw6g?

GHSA-46r8-9cj7-pw6g has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th 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-46r8-9cj7-pw6g?

GHSA-46r8-9cj7-pw6g is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-46r8-9cj7-pw6g published, and has it been updated?

GHSA-46r8-9cj7-pw6g was published on May 17, 2022 and was last updated on November 22, 2024. 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

GHSA-46r8-9cj7-pw6g — nova

Fix: openstack/nova@9f9e9da

GHSA-46r8-9cj7-pw6g is a Improper Input Validation vulnerability in nova. 2 public exploit references exist, so weaponization risk is real. A fix is available for nova — see the affected versions and patch details below.

OpenStack Compute (Nova) Improper Input Validation

Also known asCVE-2012-2654

Published

May 17, 2022

Updated

Nov 22, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

🐍nova

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

The (1) EC2 and (2) OS APIs in OpenStack Compute (Nova) Folsom (2012.2), Essex (2012.1), and Diablo (2011.3) do not properly check the protocol when security groups are created and the network protocol is not specified entirely in lowercase, which allows remote attackers to bypass intended access restrictions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nova`	all versions	12.0.0a0`pip install --upgrade 'nova==12.0.0a0'`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The (1) EC2 and (2) OS APIs in OpenStack Compute (Nova) Folsom (2012.2),…

github.comNVDAug 2017

The (1) EC2 and (2) OS APIs in OpenStack Compute (Nova) Folsom (2012.2),…

github.comNVDAug 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nova to 12.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-46r8-9cj7-pw6g 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-46r8-9cj7-pw6g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-46r8-9cj7-pw6g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-46r8-9cj7-pw6g in your dependencies?

O3 Security finds GHSA-46r8-9cj7-pw6g across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works