CVE-2026-49291
Read-scope auth bypass lets write actions via /mcp (store_memory/delete_memory).
Is CVE-2026-49291 being exploited?
Not confirmed. CVE-2026-49291 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-49291?
CVE-2026-49291 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-49291?
Yes. A fix has been recorded for CVE-2026-49291. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49291 affect?
CVE-2026-49291 affects mcp-memory-service (pre-10.65.3), AI apps utilizing MCP memory layer. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49291?
Upgrade to 10.65.3+ to fix.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthorized write via read scope enables store/delete memory, risking memory integrity and AI behavior.
Patch when possible
- affected< 10.65.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.