Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to attacker-controlled web page
-
ExploitBrowser issues cross-origin POST to /api/v1/admin/shutdown
-
ExecutionUnauthenticated endpoint accepts request (no token configured)
-
ImpactMemory Service shuts down, denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | 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. |
| Impact | 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. |
| Exploit ScenarioDerived | 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Token-less deployments of MemTensor's memmy-agent Memory Service expose POST /api/v1/admin/shutdown to unauthenticated remote requests, letting an attacker shut the service down and cause a low-impact denial of service. All versions up to 1.0.9, 1.1.1 and 1.2.2 are listed as affected (CPE: cpe:2.3:a:memtensor:memmy-agent:*), and the issue is rated only 2.3 under CVSS 4.0 (with our own assessment of 3.1/AV:N/AC:H/PR:N/UI:R/A:L) because exploitation is gated by a victim visiting an attacker-controlled page, by specific browser cross-origin behavior, and by the admin token being left unconfigured. Publicly available exploit code exists (the upstream GitHub issue and VulDB entry), but the practical risk is limited to internet-exposed instances running in the default, token-less state - the endpoint is designed for local use and the cross-origin behavior was reportedly tightened in later changes.
RemediationAI
No vendor-released patch version is identified in the available data; the public report notes only that the project 'later received cross-origin fixes', so confirm the fixed build against the upstream advisory and issue #468 (https://github.com/MemTensor/memmy-agent/issues/468, https://vuldb.com/vuln/422276) before relying on a specific release. The single most effective control is to configure an admin token so requireAdminWrite no longer short-circuits into an unauthenticated accept - the trade-off is that every admin client must then supply the token. Additionally, bind the Memory Service to loopback (127.0.0.1) instead of 0.0.0.0, since the endpoint is designed for local use; this breaks legitimate remote administration but removes network reachability. If the service must be networked, block /api/v1/admin/* at a reverse proxy or WAF and reject cross-origin POSTs, accepting that the proxy becomes a required part of the deployment. Finally, avoid leaving the default token-less configuration on any internet-exposed host, as that is the only realistic attack surface for this publicly available exploit code.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
memmy-agent's Memory Service is a TypeScript/Node HTTP server (Memory/src/server/http.ts) whose requireAdminWrite guard is responsible for gating administrative routes. When no admin token is configured - the default state for the documented local-use deployment - the guard degrades into a no-op and administrative endpoints such as POST /api/v1/admin/shutdown accept requests from any origin. The weakness class is CWE-400 (Uncontrolled Resource Consumption): rather than corrupting data or leaking information, the call terminates the process, removing availability for whatever clients depend on it. Because the route is reachable over HTTP, the CVSS 4.0 vector marks AV:N, but AC:H, UI:P and the low availability-only impact reflect that a successful attack realistically requires luring a victim's browser into issuing a cross-origin request and depends on browser-specific cross-origin semantics that the project later hardened. Confidentiality and integrity are unaffected in both the vendor and our assessed vectors (VC:N/VI:N/SC:N/SI:N).
Know when Memmy Agent gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
Cross-origin trigger needs victim interaction (UI:R) and specific browser behavior plus token-less config (AC:H); unauthenticated when no token (PR:N); only a partial DoS, so A:L and C/I:N.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A weakness has been identified in MemTensor memmy-agent up to 1.0.9/1.1.1/1.2.2. The impacted element is the function requireAdminWrite of the file Memory/src/server/http.ts of the component Memory Service. This manipulation causes resource consumption. Remote exploitation of the attack is possible. The attack is considered to have high complexity. The exploitability is regarded as difficult. The exploit has been made available to the public and could be used for attacks. The exploit is partially overstated. While "POST /api/v1/admin/shutdown" accepts unauthenticated requests when no token is configured, it’s designed for local use and later received cross-origin fixes. Unauthenticated endpoint exposure is confirmed; browser-triggered DoS remains likely but depends on specific browser behavior.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-104413
GHSA-ch9f-9wc3-mgg4
NVD
CVE.org
EPSS
VulDB
Exploit-DB