Yawkat lz4-java
yawkat LZ4 Java: Native library extraction to a shared temporary directory is vulnerable to file replacement by another local user
yawkat LZ4 Java provides LZ4 compression for Java. From 1.7.0 until 1.11.4, net.jpountz.util.Native.load() uses File.createTempFile to create an exclusive temporary .lck file but derives the native-library path by removing the suffix, then FileOutputStream opens that predictable path without exclusive creation, allowing another local user with access to the same shared temporary directory to create or replace the library file before System.load() uses it. Successful exploitation depends on shared-directory permissions, host protections, and winning the race, and can execute native code as the victim; hardened systems may instead cause library loading to fail and fall back to Java implementations. Configurations using a system library, a private java.io.tmpdir, or Java-only implementations are not affected. This issue is fixed in version 1.11.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.11.4
Fixed in 1.11.4
Mitigation
Upgrade lz4-java to 1.11.4 or later.
References
- Vendor advisory github.com/yawkat/lz4-java/security/advisories…
- Patch github.com/yawkat/lz4-java/commit/7a48b7f6b809…
- Release notes github.com/yawkat/lz4-java/releases/tag/v1.11.…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending
Pending 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| federiconbaez/cortex9-lz4java-tmp-native-lib-predictable-name-model | 9 Nov 2026 +34 d | 14 Nov 2026 | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.