Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107206 critical CVSS 9.4

Vulnerability in LMCache (CVE-2026-107206)

Summary

Vulnerability in LMCache (CVE-2026-107206). Confidential information can be exposed externally. Exploitable via GET /env.

Original description

The description as published by the source.

LMCache through 0.5.5 contains a missing authentication vulnerability in the multiprocess mode HTTP server that allows remote unauthenticated attackers to access management endpoints listening on all interfaces by default. Attackers can read environment credentials via GET /env and configuration via GET /config, clear caches, delete cache objects, and modify tenant quotas to evict other tenants' cached data.

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-107206 has been found in LMCache.
Attackers can target a specific entry point like GET /env over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "LMCache CVE-2026-107206" on the vendor's site.

CVE-2026-107206 (LMCache) — CWE-306 / CVSS v3 9.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /env / GET /config
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-306) exists in LMCache. Attackers reach the vulnerable code path via GET /env without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of LMCache. Attack surface: GET /env / GET /config.

🔥 Severity

Severity: Critical (CVSS 9.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 GET /env requests with malformed payloads or SQL meta-characters. Run grep -r 'LMCache' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'LMCache' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で LMCache を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /env' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /env への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against GET /env on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details