CVE-2026-87825

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.7Exploit: Elevated riskExposed 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.7HIGHhigh confidence
EG Risk
51
EG Risk 51/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (8)

Auto-updated Sep 9, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

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
generic

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
generic

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
generic

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 Patch Available🟡 PoC Available

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

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

Vendor Advisories for CVE-2026-87825(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatzstd-jni2026-09-24redhat

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 42× in last 7d / 124× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 124 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-87825?
CVE-2026-87825 is a high vulnerability 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 disclosed?
CVE-2026-87825 was first published on September 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (8th 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.

Book a Demo →Browse All CVEs