CVE-2025-9288Public exploitNetwork attack vector

Hash manipulation and hangs via unchecked array-likes

Published Aug 20, 2025 · Updated Aug 20, 2025

Improper input validation in Browserify sha.js 2.4.11 and earlier allows remote attackers to corrupt hash results via crafted array-like input. Hash.prototype.update accepts non-string objects without converting or validating them as buffers, then trusts attacker-controlled length and indexed values, enabling state rewind, collisions, or a hang. Exposure requires a consuming application to pass attacker-controlled array-like data into the hashing API; impacts include incorrect security decisions and service interruption.

CVSS severity9.1
Critical
EPSS probability0.68%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper input validation in Browserify sha.js 2.4.11 and earlier allows remote attackers to corrupt hash results via crafted array-like input. Hash.prototype.update accepts non-string objects without converting or validating them as buffers, then trusts attacker-controlled length and indexed values, enabling state rewind, collisions, or a hang. Exposure requires a consuming application to pass attacker-controlled array-like data into the hashing API; impacts include incorrect security decisions and service interruption.

The record

CVE
CVE-2025-9288
Published
Aug 20, 2025
Updated
Aug 20, 2025
Vendor
Browserify
Product
sha.js
Classifications
CWE-20, CAPEC-153, T1499, T1565
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 20, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=2.4.11

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Browserify · sha.jsversion=0 <=2.4.11

Published CVSS scores

9.1harborist CNACVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:H/SI:H/SA:N
9.1NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-20Improper Input Validation
CAPEC-153Input Data Manipulation
T1499Endpoint Denial of Service
T1565Data Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo