PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-87795 luben CVE debrief

The CVE-2026-87795 vulnerability in zstd-jni versions before 1.5.7-14 allows out-of-bounds memory reads due to improper validation of offset and length parameters in the ZstdDictCompress constructor. This can lead to JVM crashes when attackers supply untrusted values. The vulnerability is caused by a lack of validation of offset and length parameters, which can lead to out-of-bounds memory reads. Defenders should prioritize updates and validate offset and length parameters in the ZstdDictCompress constructor.

Vendor
luben
Product
zstd-jni
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-09
Original CVE updated
2026-09-14
Advisory published
2026-09-09
Advisory updated
2026-09-14

Who should care

Defenders responsible for maintaining and securing systems that use zstd-jni should assess exposure and prioritize updates. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Defenders should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

The CVE-2026-87795 vulnerability in zstd-jni versions before 1.5.7-14 allows out-of-bounds memory reads, potentially causing JVM crashes. Defenders should prioritize updates and validate offset and length parameters.

  • Potential JVM crashes due to out-of-bounds memory reads
  • Need to validate offset and length parameters in the ZstdDictCompress constructor
  • Priority on updating to version 1.5.7-14 or later

Technical summary

The ZstdDictCompress constructor in zstd-jni versions before 1.5.7-14 fails to validate offset and length parameters, allowing out-of-bounds memory reads. This can lead to JVM crashes when attackers supply untrusted values. The vulnerability is caused by a lack of validation of offset and length parameters, which can lead to out-of-bounds memory reads. Defenders should prioritize updates and validate offset and length parameters in the ZstdDictCompress constructor. The official CVE Program record and NIST NVD detail page provide additional information on the vulnerability.

Defensive priority

Defenders should prioritize updating to version 1.5.7-14 or later to mitigate this vulnerability.

Recommended defensive actions

  • Update to version 1.5.7-14 or later
  • Review and validate offset and length parameters in the ZstdDictCompress constructor
  • Monitor for potential JVM crashes
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is caused by a lack of validation of offset and length parameters in the ZstdDictCompress constructor, which can lead to out-of-bounds memory reads. The CVE record was published on 2026-09-09T10:22:34.557Z and has not been modified since then. The official CVE Program record and NIST NVD detail page provide additional information on the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-87795 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-87795

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-87795 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-87795

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.