Memmy Agent CVE-2026-112157

Requires that the Memory Service's admin endpoint POST /api/v1/admin/shutdown be reachable with NO admin token configured - the endpoint is designed for local use and only accepts unauthenticated requests in that default/unconfigured state. Exploitation is further gated by UI:P (a victim must visit an attacker-controlled page that issues the cross-origin request) and by specific browser cross-origin behavior, which the source notes received later fixes. Limiting factors: configuring an admin token closes unauthenticated access; the cross-origin fixes mitigate browser triggering; high attack complexity (AC:H) and the local-use design mean internet-exposed, token-less instances are the only realistically affected deployments. Affected versions: memmy-agent up to 1.0.9 / 1.1.1 / 1.2.2.

This is a low-priority issue despite being a publicly-disclosed vulnerability with available exploit code. The CVSS 4.0 base score is only 2.3, and every signal points to limited real-world risk: the vector is AV:N (network) but AC:H (high complexity), AT:N, PR:N (no auth when no token is set), UI:P (passive user interaction required), and the only impact is VA:L - a partial availability loss (DoS) with zero confidentiality or integrity impact (VC:N/VI:N). The VulDB exploit maturity is E:P (proof-of-concept), consistent with the POC=YES / KEV=NO inputs. No EPSS score was provided, but the combination of high attack complexity, dependency on specific browser behavior for cross-origin triggering, and the fact that the endpoint is 'designed for local use' strongly suggests low practical exploitation probability. Notably, the source itself states the exploit is 'partially overstated': the unauthenticated endpoint exposure is confirmed, but the browser-triggered DoS is only 'likely' and conditional. There is no CISA KEV listing and no evidence of active exploitation - this is a POC-only issue, which must not be conflated with in-the-wild use. Verdict: a real but minor hardening/DoS finding, not an urgent patch priority.

An attacker hosts a malicious web page and lures a user who has a memmy-agent Memory Service running locally (with no admin token configured) into visiting it. The page issues a cross-origin POST to /api/v1/admin/shutdown, which the unauthenticated endpoint honors and shuts the service down, causing a denial of service. A public proof-of-concept exists (GitHub issue #468), though reliable triggering depends on specific browser cross-origin behavior.