How severe is GHSA-cjgq-5qmw-rcj6?

No CVSS score has been assigned to GHSA-cjgq-5qmw-rcj6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cjgq-5qmw-rcj6?

GHSA-cjgq-5qmw-rcj6 affects the following packages: keras (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-cjgq-5qmw-rcj6?

No patched version of keras has shipped for GHSA-cjgq-5qmw-rcj6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-cjgq-5qmw-rcj6 in my PyPI dependencies?

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

How do I mitigate GHSA-cjgq-5qmw-rcj6 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-cjgq-5qmw-rcj6?

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

Is GHSA-cjgq-5qmw-rcj6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cjgq-5qmw-rcj6 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-cjgq-5qmw-rcj6?

GHSA-cjgq-5qmw-rcj6 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th 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-cjgq-5qmw-rcj6?

GHSA-cjgq-5qmw-rcj6 is classified as CWE-494 (CWE-494). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cjgq-5qmw-rcj6 published, and has it been updated?

GHSA-cjgq-5qmw-rcj6 was published on January 8, 2025 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.

🐍 PyPI

Not in CISA KEV

GHSA-cjgq-5qmw-rcj6 — keras

GHSA-cjgq-5qmw-rcj6 is a CWE-494 vulnerability in keras. No vendor fix is recorded yet; mitigation options are listed below.

keras Path Traversal vulnerability

Also known asCVE-2024-55459PYSEC-2025-121

Published

Jan 8, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cjgq-5qmw-rcj6.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

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

🐍keras

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

An issue in keras 3.7.0 allows attackers to write arbitrary files to the user's machine via downloading a crafted tar file through the get_file function.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keras`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keras, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of keras has shipped for GHSA-cjgq-5qmw-rcj6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-cjgq-5qmw-rcj6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cjgq-5qmw-rcj6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue in keras 3.7.0 allows attackers to write arbitrary files to the user's machine via downloading a crafted tar file through the get_file function.

O3 Security · Impact-Aware SCA

Is GHSA-cjgq-5qmw-rcj6 in your dependencies?

O3 Security finds GHSA-cjgq-5qmw-rcj6 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