CVE-2026-49291

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

mcp-memory-service is a semantic memory layer for AI applications. Prior to version 10.65.3, the HTTP MCP JSON-RPC endpoint at /mcp requires only OAuth read scope for all requests, then dispatches tools/call directly to handlers that include mutating tools. A read-only OAuth client can call store_memory and delete_memory through MCP even though the corresponding REST endpoints require write scope. Version 10.65.3 patches the issue.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
17.8%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
No patch confirmed yet.
generic

GitHub - doobidoo/mcp-memory-service: Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation. · GitHub

https://web.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service/

Vendor Advisories for CVE-2026-49291(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 06:58 UTCEG score recompute
  2. 2026-07-06 18:57 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 06:55 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 19:11 UTCEG score recompute
  7. 2026-07-05 07:26 UTCEG score recompute
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 19:36 UTCEG score recompute
  10. 2026-07-04 07:50 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 19:14 UTCEG score recompute
  13. 2026-07-03 07:29 UTCEG score recompute
  14. 2026-07-02 19:46 UTCEG score recompute
  15. 2026-07-02 08:01 UTCEG score recompute
  16. 2026-07-01 20:18 UTCEG score recompute
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 08:33 UTCEG score recompute
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 20:49 UTCEG score recompute
  21. 2026-06-30 09:06 UTCEG score recompute
  22. 2026-06-29 21:22 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 09:38 UTCEG score recompute
Show 22 more
  1. 2026-06-28 21:54 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 10:10 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 22:26 UTCEG score recompute
  7. 2026-06-27 10:42 UTCEG score recompute
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 22:58 UTCEG score recompute
  10. 2026-06-26 11:15 UTCEG score recompute
  11. 2026-06-25 18:50 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 07:06 UTCEG score recompute
  14. 2026-06-24 19:22 UTCEG score recompute
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-24 06:56 UTCEG score recompute
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 19:10 UTCEG score recompute
  20. 2026-06-23 07:26 UTCEG score recompute
  21. 2026-06-22 19:38 UTCEG score recompute
  22. 2026-06-22 19:38 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-49291?
CVE-2026-49291 is a high vulnerability published on June 19, 2026. mcp-memory-service is a semantic memory layer for AI applications. Prior to version 10.65.3, the HTTP MCP JSON-RPC endpoint at /mcp requires only OAuth read scope for all requests, then dispatches tools/call directly to handlers that include mutating tools. A read-only OAuth client can call…
When was CVE-2026-49291 disclosed?
CVE-2026-49291 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49291 actively exploited?
CVE-2026-49291 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49291?
CVE-2026-49291 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-49291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49291, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49291

Explore →

Is Your Infrastructure Affected by CVE-2026-49291?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.