CVE-2025-9288

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-08-21. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS
Elevated

Also known asEUVD-2025-25403 (ENISA EUVD) · GHSA-95m3-7q98-8xr5 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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

CVSS
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 20, 2025

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github, github_pr.
GitHub advisoryMentions a patch (unverified)

Missing type checks can allow types other than a well-formed `Buffer` or `string`, resulting in undefined behaviour · Advisory · browserify/sha.js · GitHub

https://github.com/browserify/sha.js/security/advisories/GHSA-95m3-7q98-8xr5
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4302-1] node-sha.js security update

https://lists.debian.org/debian-lts-announce/2025/09/msg00016.html
GitHub pull request

support multi-byte wide typed arrays

Fix merged in browserify/sha.js PR #78 on 2025-07-01 — awaiting tagged release

https://github.com/browserify/sha.js/pull/78

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunode-sha.js (2.4.11+~2.4.0-2+deb13u1build0.25.04.1) @ plucky2026-11-10ubuntu
redhatrhacm2/acm-grafana-rhel9:17835788472026-07-16redhat
redhatopenshift-pipelines/pipelines-hub-ui-rhel8:17720364712026-03-04redhat
redhatrhacm2/console-rhel9:17680019802026-01-15redhat
redhatmulticluster-engine/console-mce-rhel9:17658293332026-01-15redhat
redhatmulticluster-engine/console-mce-rhel9:v2.62025-12-17redhat
redhatrhacm2/console-rhel9:v2.112025-12-17redhat
redhatopenshift-pipelines/pipelines-hub-api-rhel9:v1.19.4-17648188802025-12-09redhat
redhatmulticluster-engine/console-mce-rhel9:v2.92025-10-30redhat
redhatrhacm2/console-rhel9:v2.142025-10-30redhat
redhatmulticluster-engine-work-container-v2.7.6-32025-10-21redhat
redhatthanos-receive-controller-container-v2.12.5-32025-10-21redhat
redhatrhdh/rhdh-hub-rhel9:1.7.1-17579630432025-09-16redhat
redhatdevspaces/machineexec-rhel9:3.23-17565095512025-09-15redhat
redhatrhdh/rhdh-hub-rhel9:1.6.4-17562411912025-08-27redhat
redhatrhtas/rekor-search-ui-rhel9:1.2.1-17554567402025-08-25redhat
npmsha.js @ 2.4.12 (fixes <= 2.4.11)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-sha.js2.4.11-2
  • every version up to 2.4.11-2+deb11u1: fixed in 2.4.11-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-sha.js2.4.11+~2.4.0-2
  • every version up to 2.4.11+~2.4.0-2+deb12u1: fixed in 2.4.11+~2.4.0-2+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-sha.js2.4.11+~2.4.0-2
  • every version up to 2.4.11+~2.4.0-2+deb13u1: fixed in 2.4.11+~2.4.0-2+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-sha.js2.4.11+~2.4.0-2
  • every version up to 2.4.12+~3.0.5-1: fixed in 2.4.12+~3.0.5-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
sha.js—
  • every version up to 2.4.12: fixed in 2.4.12
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 268 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 168 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 22:42 UTCEchelonGraph re-scored
  2. 2026-11-12 22:42 UTCVendor advisory
  3. 2026-11-12 22:42 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  5. 2026-11-11 23:04 UTCEchelonGraph re-scored
  6. 2026-11-11 23:04 UTCVendor advisory
  7. 2026-11-11 23:04 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  9. 2026-11-10 23:43 UTCEchelonGraph re-scored
  10. 2026-11-10 23:43 UTCVendor advisory
  11. 2026-11-10 23:43 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  13. 2026-11-10 00:21 UTCEchelonGraph re-scored
  14. 2026-11-10 00:21 UTCVendor advisory
  15. 2026-11-10 00:21 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  17. 2026-11-09 01:00 UTCEchelonGraph re-scored
  18. 2026-11-09 01:00 UTCVendor advisory
  19. 2026-11-09 01:00 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  21. 2026-11-08 01:39 UTCEchelonGraph re-scored
  22. 2026-11-08 01:39 UTCVendor advisory
  23. 2026-11-08 01:39 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  25. 2026-11-07 02:17 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 02:17 UTCVendor advisory
  2. 2026-11-07 02:17 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-11-06 02:56 UTCEchelonGraph re-scored
  5. 2026-11-06 02:56 UTCVendor advisory
  6. 2026-11-06 02:56 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-11-05 20:25 UTCOSV refresh
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  9. 2026-11-05 03:35 UTCEchelonGraph re-scored
  10. 2026-11-05 03:35 UTCVendor advisory
  11. 2026-11-05 03:35 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  13. 2026-11-04 04:13 UTCEchelonGraph re-scored
  14. 2026-11-04 04:13 UTCVendor advisory
  15. 2026-11-04 04:13 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  17. 2026-11-03 04:47 UTCEchelonGraph re-scored
  18. 2026-11-03 04:47 UTCVendor advisory
  19. 2026-11-03 04:47 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  21. 2026-11-02 05:25 UTCEchelonGraph re-scored
  22. 2026-11-02 05:25 UTCVendor advisory
  23. 2026-11-02 05:25 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  25. 2026-11-01 08:01 UTCGHSA enrichmentGHSA-95m3-7q98-8xr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  26. 2026-11-01 08:01 UTCEchelonGraph re-scored
  27. 2026-11-01 06:04 UTCEchelonGraph re-scored
  28. 2026-11-01 06:04 UTCVendor advisory
  29. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  30. 2026-10-31 06:42 UTCEchelonGraph re-scored
  31. 2026-10-31 06:42 UTCVendor advisory
  32. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  33. 2026-10-30 07:20 UTCEchelonGraph re-scored
  34. 2026-10-30 07:20 UTCVendor advisory
  35. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  36. 2026-10-29 07:59 UTCEchelonGraph re-scored
  37. 2026-10-29 07:59 UTCVendor advisory
  38. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  39. 2026-10-28 08:37 UTCEchelonGraph re-scored
  40. 2026-10-28 08:37 UTCVendor advisory
  41. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  42. 2026-10-27 08:51 UTCEchelonGraph re-scored
  43. 2026-10-27 08:51 UTCVendor advisory
  44. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  45. 2026-10-26 07:57 UTCEchelonGraph re-scored
  46. 2026-10-26 07:57 UTCVendor advisory
  47. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  48. 2026-10-25 15:59 UTCEchelonGraph re-scored
  49. 2026-10-25 08:34 UTCEchelonGraph re-scored
  50. 2026-10-25 08:34 UTCVendor advisory
  51. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  52. 2026-10-24 09:13 UTCEchelonGraph re-scored
  53. 2026-10-24 09:13 UTCVendor advisory
  54. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  55. 2026-10-23 09:51 UTCEchelonGraph re-scored
  56. 2026-10-23 09:51 UTCVendor advisory
  57. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  58. 2026-10-22 10:27 UTCEchelonGraph re-scored
  59. 2026-10-22 10:27 UTCVendor advisory
  60. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  61. 2026-10-21 11:02 UTCEchelonGraph re-scored
  62. 2026-10-21 11:02 UTCVendor advisory
  63. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  64. 2026-10-20 11:40 UTCEchelonGraph re-scored
  65. 2026-10-20 11:40 UTCVendor advisory
  66. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  67. 2026-10-19 12:18 UTCEchelonGraph re-scored
  68. 2026-10-19 12:18 UTCVendor advisory
  69. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  70. 2026-10-18 10:28 UTCVendor advisory
  71. 2026-10-18 05:13 UTCEchelonGraph re-scored
  72. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  73. 2026-10-17 07:34 UTCEchelonGraph re-scored
  74. 2026-10-17 07:34 UTCVendor advisory
  75. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile

Frequently asked(5)

What is CVE-2025-9288?
CVE-2025-9288 is a critical-severity vulnerability; its CVE record was published on August 20, 2025. Improper Input Validation vulnerability in sha.js allows Input Data Manipulation.This issue affects sha.js: through 2.4.11.
When was the CVE record for CVE-2025-9288 published?
The CVE record for CVE-2025-9288 was published on August 20, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-9288 actively exploited?
CVE-2025-9288 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-9288?
CVE-2025-9288 has a CVSS base score of 9.1 (NVD).
How do I remediate CVE-2025-9288?
A fix for CVE-2025-9288 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-9288 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-9288

Explore →

Is Your Infrastructure Affected by CVE-2025-9288?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.