CVE-2026-106451
yawkat LZ4 Java provides LZ4 compression for Java. From 1.7.0 until …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/yawkat/lz4-java/commit/7a48b7f6b8099b9dab6541e4ac2ee0979dc55aa3
- github.com/yawkat/lz4-java/releases/tag/v1.11.4
- github.com/yawkat/lz4-java/security/advisories/GHSA-mcr4-qmvw-px4g
- nvd.nist.gov/vuln/detail/CVE-2026-106451
- github.com/advisories/GHSA-mcr4-qmvw-px4g
- nvd.nist.gov/vuln/detail/CVE-2026-106451
- cve.org/CVERecord?id=CVE-2026-106451
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.