CVE-2026-106451
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 1% of all known CVEs.
References
Related Vulnerabilities
Other CWE-367 (TOCTOU Race Condition) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-36980 | High | 8.1 | 82% | - | Fix |
| CVE-2024-30088 | High | 7.0 | 68% | KEV + Ransom | Fix |
| CVE-2004-0594 | Medium | 5.1 | 55% | - | Fix |
| CVE-2025-34027 | Critical | 9.0 | 46% | - | - |
| CVE-2024-0132 | Critical | 9.0 | 41% | - | Fix |
| CVE-2023-38146 | High | 8.8 | 37% | - | Fix |
Common questions
How do I fix CVE-2026-106451?
No published fix for CVE-2026-106451 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-106451 being actively exploited?
Not that we know of. CVE-2026-106451 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.11% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.
How severe is CVE-2026-106451?
CVE-2026-106451 has a CVSS v4 base score of 7.3, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-106451
Markdown
[](https://tridentstack.com/cve/CVE-2026-106451)HTML
<a href="https://tridentstack.com/cve/CVE-2026-106451"><img src="https://tridentstack.com/cve/badge/CVE-2026-106451.svg" alt="CVE-2026-106451"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-07.