CVE-2026-49291
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedmcp-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe MCP JSON-RPC endpoint at /mcp requires only OAuth read scope for all requests, but then dispatches tools/call directly to handlers including mutating tools like store_memory and delete_memory. This allows read-only OAuth clients to bypass authorization and call these mutating operations via MCP even though the corresponding REST endpoints correctly enforce write scope requirements.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if MCP endpoint is enabledCheck your server configuration or running services for the /mcp JSON-RPC endpoint exposureAffected if The /mcp endpoint is publicly or internally accessible and OAuth-protected
-
Check OAuth scope configuration for MCPInspect your OAuth configuration for the MCP endpoint to determine which scopes are being enforced - look for whether read and write scopes are differentiatedAffected if The MCP endpoint accepts only 'read' scope for all requests including mutating operations
-
Verify version against fixed releaseLocate the installed software version and compare to 10.65.3Affected if The installed version is earlier than 10.65.3
-
Test read-only OAuth client accessUse a client configured with only 'read' scope to call mutating MCP tools such as store_memory or delete_memory through the /mcp endpointAffected if A read-only OAuth client can successfully invoke mutating tools through the MCP interface
You are affected if the /mcp JSON-RPC endpoint is enabled, accepts only 'read' scope for all operations, and the installed version is earlier than 10.65.3, allowing read-only OAuth clients to mutate data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade mcp-memory-service to version 10.65.3 or later which patches this authorization bypass. After upgrading, verify that OAuth read-scope clients can no longer invoke mutating MCP tools.
10.65.3
- 1. Identify the current version of mcp-memory-service in use
- 2. Upgrade mcp-memory-service to version 10.65.3 or later
- 3. Verify the upgrade was successful by checking the installed version
- 4. Confirm that OAuth read-only clients can no longer access mutating tools like store_memory and delete_memory through the MCP endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49291 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data