# yawkat LZ4 Java: LZ4DecompressorWithLength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 GiB allocation and OutOfMemoryError Advisory record · `GHSA-6cx8-rjf8-pr8g` - **Identifiers:** `GHSA-6cx8-rjf8-pr8g` · `CVE-2026-106453` - **State:** Confirmed - **Severity:** CVSS 5.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-789](https://cwe.mitre.org/data/definitions/789.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) - **Published:** 7 Oct 2026 - **Updated:** 7 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 Oct 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `at.yawk.lz4:lz4-java` (Maven): affected `<1.11.2`; fixed in `1.11.2` - `org.lz4:lz4-java` (Maven): affected `<=1.8.1`; no fixed version yet ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Versions of at.yawkat LZ4 Java before 1.11.2 are affected; the fix is in 1.11.2, so upgrade to that version. The org.lz4:lz4-java package at 1.8.1 and earlier is also affected, and the source lists no fixed version for it. In both cases, an attacker who can supply LZ4 data to the decompressor's length-header convenience methods can send a 5-byte input that makes the JVM allocate up to about 1 GiB, which can cause an OutOfMemoryError or heap exhaustion. Wait, that's a fourth sentence; I need to keep to two or three. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0037, the 31st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6cx8-rjf8-pr8g) ## Sources - [GitHub Advisory Database: GHSA-6cx8-rjf8-pr8g](https://github.com/advisories/GHSA-6cx8-rjf8-pr8g) - [OSV: GHSA-6cx8-rjf8-pr8g](https://osv.dev/vulnerability/GHSA-6cx8-rjf8-pr8g) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .