Vulnerabilities

Security fix · CVE-2026-93451

snappy-java: Heap buffer overflow in Snappy.uncompress*Array typed-array methods

Published Oct 27, 2026 · catalog updated Oct 27, 2026 · snappy-java: Heap buffer overflow

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-93451. EPSS is 0.30%. Act only if a listed version of snappy-java: Heap buffer overflow is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (snappy-java: Heap buffer overflow).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.30%
Remediation
Version ranges on file
Affected products
maven org.xerial.snappy · maven org.xerial.snappy:snappy-java

### Impact , , , , and sized the result array by dividing the declared uncompressed byte length by the element size, but native code wrote the full byte length. If the declared length is not a multiple of the element size, up to 7 bytes are written past the end of the Java array, corrupting the heap. ### Patches Fixed in 1.1.10.9 ([#739](https://github.com/xerial/snappy-java/pull/739)). These methods now reject uncompressed lengths that are not a multiple of the element size with . ### Workarounds Check that is a multiple of the element size before calling these methods.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • maven org.xerial.snappyversion unspecified
  • maven org.xerial.snappy:snappy-java<= 1.1.10.8

How to fix CVE-2026-93451

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-93451. EPSS is 0.30%. Act only if a listed version of snappy-java: Heap buffer overflow is installed.

Which versions are affected?

Compare what you have installed with <= 1.1.10.8. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-193; CWE-787: Out-of-bounds Write. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 27, 2026 · GitHub Advisory Database

    Detected

    ### Impact , , , , and sized the result array by dividing the declared uncompressed byte length by the element size, but native code wrote the full byte length. If the declared length is not a multiple of the element size, up to 7 bytes are written past the end of the Java array, corrupting the heap. ### Patches Fixed in 1.1.10.9 ([#739](https://github.com/xerial/snappy-java/pull/739)). These meth

  2. Oct 27, 2026 · GitHub Advisory Database

    Updated

    ### Impact , , , , and sized the result array by dividing the declared uncompressed byte length by the element size, but native code wrote the full byte length. If the declared length is not a multiple of the element size, up to 7 bytes are written past the end of the Java array, corrupting the heap. ### Patches Fixed in 1.1.10.9 ([#739](https://github.com/xerial/snappy-java/pull/739)). These meth

Sources

  • CVE.orgVulnerability recordCVE-2026-93451

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-93451

    30-day exploitation probability 0.30%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-gwq9-9ffj-mvrv

    snappy-java: Heap buffer overflow in Snappy.uncompress*Array typed-array methods

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-93451

    Snappy.uncompressCharArray, uncompressShortArray, uncompressIntArray, uncompressLongArray, uncompressFloatArray and uncompressDoubleArray sized the result array by dividing the declared uncompressed byte length by the element size, but native code wrote the full byte length. If the declared length is not a multiple of the element size, up to 7 bytes are written past the end of the Java array, corr

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 28, 2026
  • GitLab Advisory DatabaseOct 28, 2026
  • CVE.orgOct 27, 2026
  • GitHub Advisory DatabaseOct 27, 2026