Skip to main content
VulnerabilityPublished

CVE-2026-107207: LMCache through 0.5.5 contains a server-side request forgery vulnerability in its frontend monitoring service that allows unauthenticated attackers

Affects LMCacheSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHublmcache/LMCachepkg:github/lmcache/LMCacheOther threatsAffected
  • <=0.5.5
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the frontend monitoring service endpoints and monitor for suspicious POST requests to /api/proxies. Consider network-level controls to limit exposure of internal hosts accessible via /proxy and /proxy2 endpoints.

Description

LMCache versions through 0.5.5 have a server-side request forgery (SSRF) vulnerability in the frontend monitoring service. This flaw allows unauthenticated attackers to bypass the proxy allowlist by registering arbitrary hosts via a POST request to /api/proxies. Subsequently, attackers can use the /proxy or /proxy2 endpoints to access internal hosts, read their responses, and interfere with node operations or heartbeat signals.

References

Community reviews

Loading reviews…