snappy-java through 1.1.10.8 contains a buffer overflow vulnerability in typed Snappy.uncompress*Array methods that allocate output arrays by dividing uncompressed length by element size but pass the undivided length to native code. Attackers controlling compressed input can cause misaligned length values to write past array bounds with attacker-controlled bytes, corrupting heap memory.
CVE-2026-93451
Score 6.5 from GitHub Security Advisory published 2026-09-18. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
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 computedSeverity65% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 22, 2026
Advisory Details (4)
Auto-updated Sep 17, 2026snappy-java through 1.1.10.8 Buffer Overflow via typed uncompress methods | Advisories | VulnCheck
https://www.vulncheck.com/advisories/snappy-java-through-1.1.10.8-buffer-overflow-via-typed-uncompress-methodsGitHub - xerial/snappy-java: Snappy compressor/decompressor for Java · GitHub
https://github.com/xerial/snappy-javasnappy-java/src/main/java/org/xerial/snappy/Snappy.java at v1.1.10.8 · xerial/snappy-java · GitHub
https://github.com/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L802snappy-java through 1.1.10.8 Heap Buffer Overflow via uncompress*Array (truncated output allocation) · Issue #729 · xerial/snappy-java · GitHub
https://github.com/xerial/snappy-java/issues/729Vendor Advisories for CVE-2026-93451(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 22× in last 7d / 25× 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.
- 2026-09-24 22:59 UTCEG score recompute
- 2026-09-24 22:59 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 21:36 UTCEG score recompute
- 2026-09-23 21:36 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 20:34 UTCEG score recompute
- 2026-09-22 20:34 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:25 UTCEG score recompute
- 2026-09-21 21:25 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 20:59 UTCEG score recompute
- 2026-09-21 20:59 UTCGHSA enrichment
- 2026-09-21 03:34 UTCEG score recompute
- 2026-09-21 03:34 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 02:32 UTCEG score recompute
- 2026-09-20 02:32 UTCGHSA enrichment
- 2026-09-19 01:30 UTCEG score recompute
- 2026-09-19 01:30 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 00:28 UTCEG score recompute
- 2026-09-17 23:34 UTCEG score recompute
- 2026-09-17 23:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-93451?
When was CVE-2026-93451 disclosed?
Is CVE-2026-93451 actively exploited?
What is the CVSS score of CVE-2026-93451?
How do I remediate CVE-2026-93451?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93451
Is Your Infrastructure Affected by CVE-2026-93451?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.