How severe is CVE-2025-9288?

No CVSS score has been assigned to CVE-2025-9288 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-9288?

CVE-2025-9288 affects the following packages: sha.js (npm). Ecosystems affected: npm.

How do I fix CVE-2025-9288?

Update sha.js to 2.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9288 is resolved across your whole dependency graph.

How do I detect CVE-2025-9288 in my npm dependencies?

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

How do I mitigate CVE-2025-9288 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 CVE-2025-9288?

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

Is CVE-2025-9288 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-9288 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 CVE-2025-9288?

CVE-2025-9288 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th 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 CVE-2025-9288?

CVE-2025-9288 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 CVE-2025-9288 published, and has it been updated?

CVE-2025-9288 was published on August 20, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-9288 — sha.js

Fix: browserify/sha.js#78

CVE-2025-9288 is a Improper Input Validation vulnerability in sha.js. A fix is available for sha.js — see the affected versions and patch details below.

Missing type checks leading to hash rewind and passing on crafted data

Also known asGHSA-95m3-7q98-8xr5

Published

Aug 20, 2025

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 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 CVE-2025-9288.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

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

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

sha.jsnpm

19.5Mdownloads / week

Description

Improper Input Validation vulnerability in sha.js allows Input Data Manipulation.This issue affects sha.js: through 2.4.11.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sha.js`	all versions	2.4.12`npm install sha.js@2.4.12`

Detection & mitigation playbook

Open-source dependency

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

Tailored to CVE-2025-9288. 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 HatImportant

This vulnerability was marked as Important rather then Critical because while the lack of input type checks in sha.js allows for hash state rewinding, crafted collisions, and potential denial of service, the vulnerability requires highly specific crafted input objects that are unlikely to occur in typical real-world…

Product	Fixed in	Advisory
multicluster engine for Kubernetes 2.7 for RHEL 8	`multicluster-engine-assisted-service-8-container-v2.7.6-2`	RHSA-2025:18278
Red Hat Advanced Cluster Management for Kubernetes 2.12 for RHEL 9	`acm-cli-container-v2.12.5-4`	RHSA-2025:18744
multicluster engine for Kubernetes 2.6	`multicluster-engine/console-mce-rhel9:v2.6`	RHSA-2025:23528
multicluster engine for Kubernetes 2.8	`multicluster-engine/console-mce-rhel9:1765829333`	RHSA-2026:0722
multicluster engine for Kubernetes 2.9	`multicluster-engine/console-mce-rhel9:v2.9`	RHSA-2025:19332
Red Hat Advanced Cluster Management for Kubernetes 2.11	`rhacm2/console-rhel9:v2.11`	RHSA-2025:23529
Red Hat Advanced Cluster Management for Kubernetes 2.11	`rhacm2/acm-grafana-rhel9:1783578847`	RHSA-2026:41064
Red Hat Advanced Cluster Management for Kubernetes 2.13	`rhacm2/console-rhel9:1768001980`	RHSA-2026:0627

Ubuntu

USN-7778-1Ubuntu

Frequently Asked Questions

Improper Input Validation vulnerability in sha.js allows Input Data Manipulation.This issue affects sha.js: through 2.4.11.

O3 Security · Impact-Aware SCA

Is CVE-2025-9288 in your dependencies?

O3 Security finds CVE-2025-9288 across npm 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