CVE-2026-90560

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-76905 (ENISA EUVD) · GHSA-392q-wrgq-6wmj (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.6%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

zstd-jni versions 1.2.0 through 1.5.7-13 contain an out-of-bounds read vulnerability in the ZstdDictDecompress constructor because offset and length arguments are never validated against the dictionary array bounds. Attackers can supply arbitrary offset or length values to read memory past the end of the supplied array, potentially causing JVM termination.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; 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 public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 12, 2026

Last Modified

September 24, 2026

Advisory Details (6)

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

zstd-jni 1.2.0 through 1.5.7-13 Out-of-Bounds Read via ZstdDictDecompress | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zstd-jni-1.2.0-through-1.5.7-13-out-of-bounds-read-via-zstddictdecompress
Web page

zstd-jni Missing Bounds Check on ZstdDictDecompress Constructor · Issue #405 · luben/zstd-jni · GitHub

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

commit b74ab242d640 (luben/zstd-jni)

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

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

zstd-jni/src/main/java/com/github/luben/zstd/ZstdDictDecompress.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/ZstdDictDecompress.java#L49
Web page

zstd-jni/src/main/java/com/github/luben/zstd/ZstdDictDecompress.java at v1.2.0 · luben/zstd-jni · GitHub

https://github.com/luben/zstd-jni/blob/v1.2.0/src/main/java/com/github/luben/zstd/ZstdDictDecompress.java#L37
Web page

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

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

Patch Availability(14)

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

These rows come from Red Hat. 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.7-23+ds-2 (14 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.7-23+ds-2 (10 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 up to 1.5.7-23+ds-1: fixed in 1.5.7-23+ds-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 8× in last 7d / 37× 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 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). "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 209 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 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-90560?
CVE-2026-90560 is a high-severity vulnerability; its CVE record was published on September 12, 2026. zstd-jni versions 1.2.0 through 1.5.7-13 contain an out-of-bounds read vulnerability in the ZstdDictDecompress constructor because offset and length arguments are never validated against the dictionary array bounds. Attackers can supply arbitrary offset or length values to read memory past the end…
When was CVE-2026-90560 made public?
CVE-2026-90560 was made public on August 13, 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 12, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-90560 actively exploited?
CVE-2026-90560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90560?
CVE-2026-90560 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-90560?
A fix for CVE-2026-90560 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90560 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-90560

Explore →

Is Your Infrastructure Affected by CVE-2026-90560?

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