How severe is GHSA-7372-q459-jxhr?

No CVSS score has been assigned to GHSA-7372-q459-jxhr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7372-q459-jxhr?

GHSA-7372-q459-jxhr affects the following packages: pyxdg (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-7372-q459-jxhr?

Update pyxdg to 0.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7372-q459-jxhr is resolved across your whole dependency graph.

How do I detect GHSA-7372-q459-jxhr in my PyPI dependencies?

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

How do I mitigate GHSA-7372-q459-jxhr 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-7372-q459-jxhr?

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

Is GHSA-7372-q459-jxhr actively exploited in the wild?

No public exploit code has been indexed for GHSA-7372-q459-jxhr 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-7372-q459-jxhr?

GHSA-7372-q459-jxhr has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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-7372-q459-jxhr?

GHSA-7372-q459-jxhr is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7372-q459-jxhr published, and has it been updated?

GHSA-7372-q459-jxhr was published on May 17, 2022 and was last updated on December 6, 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-7372-q459-jxhr — pyxdg

Fix: takluyver/pyxdg@bd999c1

GHSA-7372-q459-jxhr is a CWE-59 vulnerability in pyxdg. A fix is available for pyxdg — see the affected versions and patch details below.

pyxdg Arbitrary File Overwrite via Race Condition

Also known asCVE-2014-1624PYSEC-2014-95

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

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

🐍pyxdg

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

Race condition in the xdg.BaseDirectory.get_runtime_dir function in pyxdg 0.25 allows local users to overwrite arbitrary files by pre-creating /tmp/pyxdg-runtime-dir-fallback-victim to point to a victim-owned location, then replacing it with a symlink to an attacker-controlled location once the get_runtime_dir function is called.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pyxdg`	all versions	0.26`pip install --upgrade 'pyxdg==0.26'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyxdg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pyxdg to 0.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7372-q459-jxhr 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-7372-q459-jxhr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-7372-q459-jxhr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Race condition in the `xdg.BaseDirectory.get_runtime_dir` function in pyxdg 0.25 allows local users to overwrite arbitrary files by pre-creating `/tmp/pyxdg-runtime-dir-fallback-victim` to point to a victim-owned location, then replacing it with a symlink to an attacker-controlled location once the `get_runtime_dir` function is called.

O3 Security · Impact-Aware SCA

Is GHSA-7372-q459-jxhr in your dependencies?

O3 Security finds GHSA-7372-q459-jxhr 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