← Back
CVE-2026-59949
medium
CVSS 6.5
Vulnerability in at.yawk.lz4:lz4-java (CVE-2026-59949)
Summary
vulnerability in at.yawk.lz4:lz4-java (CVE-2026-59949). Risk of unauthorized operations or information disclosure. Exploitable via ``off``. Mitigation: upgrade to `1.11.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59949** has been found in at.yawk.lz4:lz4-java.
Attackers can target a specific entry point like ``off`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade at.yawk.lz4:lz4-java to **1.11.1** or later.
If unsure, ask your IT team or search "at.yawk.lz4:lz4-java CVE-2026-59949" on the vendor's site.
CVE-2026-59949 (at.yawk.lz4:lz4-java) — CWE-476 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `off` / `len` / `bytes` / `XXHashJNI.XXH32_update`
Patched: `1.11.1` — 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.
❓ What is the problem
**A vulnerability** (CWE-476) exists in at.yawk.lz4:lz4-java. Attackers reach the vulnerable code path via ``off`` without authentication.
📍 Affected scope
at.yawk.lz4:lz4-java — . Attack surface: `off` / `len` / `bytes` / `XXHashJNI.XXH32_update`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.11.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'at.yawk.lz4:lz4-java' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'at.yawk.lz4:lz4-java' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `at.yawk.lz4:lz4-java` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade at.yawk.lz4:lz4-java to 1.11.1ステージング環境で 1.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
at.yawk.lz4:lz4-java
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.11.1"}]}]
maven
org.lz4:lz4-java
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]