CVE-2026-87825

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. A secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-75023 (ENISA EUVD) · GHSA-9p7w-x2w6-p34j (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
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.2%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

zstd-jni before 1.5.7-14 contains a use-after-free vulnerability where streams and contexts hold a dictionary's shared lock only during the load call, allowing the dictionary to be closed while still referenced. Attackers can close a dictionary after associating it with a stream or context, causing subsequent read or write operations to access freed native memory, resulting in silent data corruption or JVM crashes.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 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.2%
EPSS %ILE
11th
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 (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (8)

Auto-updated Sep 9, 2026
Patch available. Sources: github_commit, github.
Web page

zstd-jni 1.3.8-4 through 1.5.7-13 Use-After-Free of Compression and Decompression Dictionaries | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zstd-jni-1.3.8-4-through-1.5.7-13-use-after-free-of-compression-and-decompression-dictionaries
Web page

GitHub - luben/zstd-jni: JNI binding for Zstd · GitHub

https://github.com/luben/zstd-jni
GitHub commit

commit 0827ed02551b (luben/zstd-jni)

Fix landed in luben/zstd-jni commit 0827ed02551b — awaiting tagged release

https://github.com/luben/zstd-jni/commit/0827ed02551bbd8d6f8e4bbff99d83bf50f91938
Web page

zstd-jni/src/main/java/com/github/luben/zstd/BaseZstdBufferDecompressingStreamNoFinalizer.java at v1.5.7-13 · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/blob/v1.5.7-13/src/main/java/com/github/luben/zstd/BaseZstdBufferDecompressingStreamNoFinalizer.java
Web page

zstd-jni/src/main/java/com/github/luben/zstd/ZstdInputStreamNoFinalizer.java at v1.5.7-13 · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/blob/v1.5.7-13/src/main/java/com/github/luben/zstd/ZstdInputStreamNoFinalizer.java
GitHub commit

commit a560131d7834 (luben/zstd-jni)

Fix landed in luben/zstd-jni commit a560131d7834 — awaiting tagged release

https://github.com/luben/zstd-jni/commit/a560131d7834598afd9cea6b7c107bc88e915936
GitHub commit

commit 393d7311766a (luben/zstd-jni)

Fix landed in luben/zstd-jni commit 393d7311766a — awaiting tagged release

https://github.com/luben/zstd-jni/commit/393d7311766abbc285b149302c0fe1f94b16d555
GitHub advisoryMentions a patch (unverified)

Use-After-Free of compression/decompression dictionaries · Advisory · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/security/advisories/GHSA-947w-pxjj-c7m9

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatocp-tools-4/jenkins-rhel9:17920415142026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400812026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920407332026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400962026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443272026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920404282026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443822026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920402872026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920401312026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443262026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443862026-10-22redhat
redhatrhoai/odh-th06-rocm64-torch291-py312-rhel9:17918721192026-10-19redhat
redhatzstd-jni2026-09-24redhat
redhatcom.github.luben/zstd-jni:1.5.7.16-rhel8-redhat-000012026-09-22redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
zstd-jni-java1.5.2-5+ds-3 ... 1.5.4-2+ds-3~exp4 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
zstd-jni-java1.5.2-5+ds-7 ... 1.5.4-2+ds-3~exp4 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
zstd-jni-java1.5.2-5+ds-7 ... 1.5.4-2+ds-3~exp4 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 87× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 198 refreshes 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 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-87825?
CVE-2026-87825 is a high-severity vulnerability; its CVE record was published on September 9, 2026. zstd-jni before 1.5.7-14 contains a use-after-free vulnerability where streams and contexts hold a dictionary's shared lock only during the load call, allowing the dictionary to be closed while still referenced. Attackers can close a dictionary after associating it with a stream or context, causing…
When was CVE-2026-87825 made public?
CVE-2026-87825 was made public on August 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 9, 2026. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-87825 actively exploited?
CVE-2026-87825 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87825?
CVE-2026-87825 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87825?
A fix for CVE-2026-87825 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87825 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-2026-87825

Explore →

Is Your Infrastructure Affected by CVE-2026-87825?

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