How severe is GHSA-xjmj-p278-4jp5?

No CVSS score has been assigned to GHSA-xjmj-p278-4jp5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xjmj-p278-4jp5?

GHSA-xjmj-p278-4jp5 affects the following packages: nova (PyPI), nova (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xjmj-p278-4jp5?

Update nova to 2013.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjmj-p278-4jp5 is resolved across your whole dependency graph.

How do I detect GHSA-xjmj-p278-4jp5 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-xjmj-p278-4jp5 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-xjmj-p278-4jp5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xjmj-p278-4jp5 can be triaged on real exposure rather than presence alone.

Is GHSA-xjmj-p278-4jp5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xjmj-p278-4jp5 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-xjmj-p278-4jp5?

GHSA-xjmj-p278-4jp5 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 79th 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-xjmj-p278-4jp5?

GHSA-xjmj-p278-4jp5 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xjmj-p278-4jp5 published, and has it been updated?

GHSA-xjmj-p278-4jp5 was published on May 14, 2022 and was last updated on September 10, 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-xjmj-p278-4jp5: nova

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% 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

2 pkgs affected

🐍nova🐍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

api/metadata/handler.py in OpenStack Compute (Nova) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2, when proxying metadata requests through Neutron, makes it easier for remote attackers to guess instance ID signatures via a brute-force attack that relies on timing differences in responses to instance metadata requests.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nova`	all versions	2013.2.4`pip install --upgrade 'nova==2013.2.4'`
🐍PyPI	`nova`	≥ 2014.0.0&&< 2014.1.2	2014.1.2`pip install --upgrade 'nova==2014.1.2'`

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 2013.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjmj-p278-4jp5 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-xjmj-p278-4jp5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xjmj-p278-4jp5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

Product	Fixed in	Advisory
OpenStack 4 for RHEL 6	`openstack-nova-0:2013.2.3-12.el6ost`	RHSA-2014:1084
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-nova-0:2014.1.1-4.el7ost`	RHSA-2014:0940

Ubuntu

USN-2325-1Ubuntu

Frequently Asked Questions

api/metadata/handler.py in OpenStack Compute (Nova) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2, when proxying metadata requests through Neutron, makes it easier for remote attackers to guess instance ID signatures via a brute-force attack that relies on timing differences in responses to instance metadata requests.

O3 Security · Impact-Aware SCA

Is GHSA-xjmj-p278-4jp5 in your dependencies?

O3 Security finds GHSA-xjmj-p278-4jp5 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

GHSA-xjmj-p278-4jp5 — nova