CVE-2026-87823

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

zstd-jni before 1.5.7-14 performs 32-bit signed bounds checks on three direct-ByteBuffer frame-size native methods, allowing out-of-bounds memory reads via negative or overflowing offsets. Attackers can supply negative offset values near Integer.MIN_VALUE to read unmapped memory, causing JVM termination or extracting arbitrary frame size data from unintended memory locations.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

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
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (7)

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

zstd-jni 1.1.1 through 1.5.7-13 Out-of-Bounds Read via Direct ByteBuffer Frame-Size Methods | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zstd-jni-1.1.1-through-1.5.7-13-out-of-bounds-read-via-direct-bytebuffer-frame-size-methods
generic

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

https://github.com/luben/zstd-jni
github_commit

commit 46dcb2a54c8b (luben/zstd-jni)

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

https://github.com/luben/zstd-jni/commit/46dcb2a54c8b8f2ce2cad7187a7513f509c533ac
generic

zstd-jni/src/main/java/com/github/luben/zstd/Zstd.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/Zstd.java
generic

zstd-jni/src/main/native/jni_zstd.c at v1.5.7-13 · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/blob/v1.5.7-13/src/main/native/jni_zstd.c
github_commit

commit d7a1c99322d5 (luben/zstd-jni)

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

https://github.com/luben/zstd-jni/commit/d7a1c99322d5e1fc71932e722c0b5bb2fc525d3f
github Patch Available

Integer Overflow Bypasses Bounds Check on Direct ByteBuffer Frame-Size Queries · Advisory · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/security/advisories/GHSA-jfr6-9xqw-2g2q

Vendor Advisories for CVE-2026-87823(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 51× 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.

  1. 2026-09-21 08:15 UTCGHSA enrichment
  2. 2026-09-20 21:15 UTCEG score recompute
  3. 2026-09-20 21:15 UTCGHSA enrichment
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 10:16 UTCGHSA enrichment
  6. 2026-09-19 23:16 UTCEG score recompute
  7. 2026-09-19 23:16 UTCGHSA enrichment
  8. 2026-09-19 12:16 UTCGHSA enrichment
  9. 2026-09-19 01:16 UTCEG score recompute
  10. 2026-09-19 01:16 UTCGHSA enrichment
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 14:17 UTCGHSA enrichment
  13. 2026-09-18 03:10 UTCEG score recompute
  14. 2026-09-18 03:10 UTCGHSA enrichment
  15. 2026-09-17 19:32 UTCEPSS rescore
  16. 2026-09-17 16:10 UTCGHSA enrichment
  17. 2026-09-17 05:11 UTCGHSA enrichment
  18. 2026-09-16 18:11 UTCEG score recompute
  19. 2026-09-16 18:11 UTCGHSA enrichment
  20. 2026-09-16 14:09 UTCEPSS rescore
  21. 2026-09-16 06:42 UTCEG score recompute
  22. 2026-09-16 06:42 UTCGHSA enrichment
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-15 19:42 UTCGHSA enrichment
  25. 2026-09-15 08:40 UTCEG score recompute
Show 26 more
  1. 2026-09-15 08:40 UTCGHSA enrichment
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 21:40 UTCGHSA enrichment
  4. 2026-09-14 10:40 UTCGHSA enrichment
  5. 2026-09-13 23:40 UTCEG score recompute
  6. 2026-09-13 23:40 UTCGHSA enrichment
  7. 2026-09-13 12:40 UTCGHSA enrichment
  8. 2026-09-13 01:40 UTCEG score recompute
  9. 2026-09-13 01:40 UTCGHSA enrichment
  10. 2026-09-12 14:40 UTCGHSA enrichment
  11. 2026-09-12 03:40 UTCGHSA enrichment
  12. 2026-09-11 16:40 UTCEG score recompute
  13. 2026-09-11 16:40 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 05:40 UTCGHSA enrichment
  17. 2026-09-10 18:39 UTCGHSA enrichment
  18. 2026-09-10 07:38 UTCGHSA enrichment
  19. 2026-09-09 20:38 UTCGHSA enrichment
  20. 2026-09-09 17:29 UTCEG score recompute
  21. 2026-09-09 17:29 UTCGHSA enrichment
  22. 2026-09-09 16:37 UTCEG score recompute
  23. 2026-09-09 16:37 UTCGHSA enrichment
  24. 2026-09-09 15:28 UTCEG score recompute
  25. 2026-09-09 14:45 UTCEG score recompute
  26. 2026-09-09 14:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-87823?
CVE-2026-87823 is a high vulnerability published on September 9, 2026. zstd-jni before 1.5.7-14 performs 32-bit signed bounds checks on three direct-ByteBuffer frame-size native methods, allowing out-of-bounds memory reads via negative or overflowing offsets. Attackers can supply negative offset values near Integer.MIN_VALUE to read unmapped memory, causing JVM…
When was CVE-2026-87823 disclosed?
CVE-2026-87823 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87823 actively exploited?
CVE-2026-87823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.0% of all scored CVEs.
What is the CVSS score of CVE-2026-87823?
CVE-2026-87823 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-87823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87823, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87823

Explore →

Is Your Infrastructure Affected by CVE-2026-87823?

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

Start Free Scan →Browse All CVEs