CVE-2026-89046

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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.7%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

zstd-jni versions 1.5.5-6 through 1.5.7-13 contain an out-of-bounds read vulnerability in Zstd.getFrameContentSize that fails to validate negative srcPosition arguments. Attackers can supply negative offset values that bypass bounds checks and reach the native frame-header parser, causing out-of-bounds memory reads that lead to information disclosure or JVM crashes.

CVSS v3
8.2
EG Score
8.2HIGHhigh confidence
EG Risk
42
EG Risk 42/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
Severity82% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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 10, 2026

Last Modified

September 10, 2026

Advisory Details (6)

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

zstd-jni 1.5.5-6 through 1.5.7-13 Out-of-Bounds Read via Negative Offset | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zstd-jni-1.5.5-6-through-1.5.7-13-out-of-bounds-read-via-negative-offset
generic

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

https://github.com/luben/zstd-jni
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#L87
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#L730
github_commit

commit dd08685ef913 (luben/zstd-jni)

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

https://github.com/luben/zstd-jni/commit/dd08685ef913a32e76fb27f43470035c06758646
github Patch Available🟡 PoC Available

Negative-Offset Bypass in Zstd.getFrameContentSize Bounds Check · Advisory · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/security/advisories/GHSA-rm53-6wf5-f34m

Vendor Advisories for CVE-2026-89046(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 40× in last 7d / 118× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89046?
CVE-2026-89046 is a high vulnerability published on September 10, 2026. zstd-jni versions 1.5.5-6 through 1.5.7-13 contain an out-of-bounds read vulnerability in Zstd.getFrameContentSize that fails to validate negative srcPosition arguments. Attackers can supply negative offset values that bypass bounds checks and reach the native frame-header parser, causing…
When was CVE-2026-89046 disclosed?
CVE-2026-89046 was first published on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89046 actively exploited?
CVE-2026-89046 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89046?
CVE-2026-89046 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89046?
A fix for CVE-2026-89046 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89046 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-89046

Explore →

Is Your Infrastructure Affected by CVE-2026-89046?

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