Vulnerability in at.yawk.lz4:lz4-java (CVE-2026-106451)
Summary
Vulnerability in at.yawk.lz4:lz4-java (CVE-2026-106451). Risk of unauthorized operations or information disclosure. Exploitable via java.io.tmpdir. Mitigation: upgrade to 1.11.4 or later.
Original description
The description as published by the source.
Summary
When no system-installed liblz4-java is found, net.jpountz.util.Native.load() extracts the bundled native library to java.io.tmpdir and loads it with System.load. The path of the extracted library can be predicted before it is created, and the library file is opened without exclusive creation. Another local user who can write to the same temporary directory can therefore create the file first and control the code that is loaded.
Details
tempLibLock = File.createTempFile("liblz4-java-", "." + os().libExtension + ".lck");
tempLib = new File(tempLibLock.getAbsolutePath().replaceFirst(".lck$", ""));
// copy to tempLib
try (FileOutputStream out = new FileOutputStream(tempLib)) { ... }
...
System.load(tempLib.getAbsolutePath());
Only the .lck file is created safely, with a random name and exclusive creation. The library path is the .lck name without the .lck suffix, and nothing reserves it. new FileOutputStream(tempLib) opens it with O_CREAT|O_TRUNC and follows symlinks.
In a shared, world-writable temporary directory, another user can watch for the .lck file and create the corresponding library file before it is opened. If they win that race, they own the file. The victim then writes into the attacker-owned file, and the attacker can overwrite it again before System.load.
Whether this can be exploited depends on the host:
- With
fs.protected_regular = 0, the attacker can pre-create a world-writable file, and their code is…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106451 has been found in at.yawk.lz4:lz4-java.
Attackers can target a specific entry point like java.io.tmpdir over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade at.yawk.lz4:lz4-java to 1.11.4 or later.
If unsure, ask your IT team or search "at.yawk.lz4:lz4-java CVE-2026-106451" on the vendor's site.
CVE-2026-106451 (at.yawk.lz4:lz4-java) — CWE-367
Attack surface: java.io.tmpdir / System.load / createTempFile / java.library.path
Patched: 1.11.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-367) exists in at.yawk.lz4:lz4-java. Attackers reach the vulnerable code path via java.io.tmpdir.
Check the vendor advisory for the affected versions of at.yawk.lz4:lz4-java. Attack surface: java.io.tmpdir / System.load / createTempFile / java.library.path.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.11.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで at.yawk.lz4:lz4-java を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade at.yawk.lz4:lz4-java to 1.11.4ステージング環境で 1.11.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com