How severe is GHSA-grp5-h379-j75x?

No CVSS score has been assigned to GHSA-grp5-h379-j75x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-grp5-h379-j75x?

GHSA-grp5-h379-j75x affects the following packages: nova (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-grp5-h379-j75x?

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

How do I detect GHSA-grp5-h379-j75x 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-grp5-h379-j75x 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.

Is GHSA-grp5-h379-j75x actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-grp5-h379-j75x, including 1 in-the-wild exploitation 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-grp5-h379-j75x?

GHSA-grp5-h379-j75x has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-grp5-h379-j75x?

GHSA-grp5-h379-j75x is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-grp5-h379-j75x published, and has it been updated?

GHSA-grp5-h379-j75x was published on May 14, 2022 and was last updated on July 7, 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

OpenStack Nova live snapshots use an insecure local directoryGHSA-grp5-h379-j75x

Fix: openstack/nova@75be5ab

GHSA-grp5-h379-j75x is a CWE-264 vulnerability in nova. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for nova — see the affected versions and patch details below.

Also known asCVE-2013-7048PYSEC-2026-873

Published

May 14, 2022

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

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

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

OpenStack Compute (Nova) Grizzly 2013.1.4, Havana 2013.2.1, and earlier uses world-writable and world-readable permissions for the temporary directory used to store live snapshots, which allows local users to read and modify live snapshots.

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'`

Affected Products

1 product · 2 configurations

Application

novaopenstack

≥ 2013.2 && ≤ 2013.2.1

range

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.

OpenStack Compute (Nova) Grizzly 2013.1.4, Havana 2013.2.1, and earlier …

bugs.launchpad.netNVDNov 2018

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-grp5-h379-j75x 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.

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 3 for RHEL 6	`openstack-nova-0:2013.1.5-2.el6ost`	RHSA-2014:0366
OpenStack 4 for RHEL 6	`openstack-nova-0:2013.2.2-2.el6ost`	RHSA-2014:0231

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-grp5-h379-j75x in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works