Fix/memory server schema validation

[0dd]

TLDR

Fix the critical Security Issue see the report

• Add explicit property filtering in saveGraph method
• Add additionalProperties constraints to input schemas

Description

Server Details

• Server: Memory Server
• Changes to: Tool

Motivation and Context

Security Issue: Please Check the report

How Has This Been Tested?

Test with Amazon Q and MCP CLI

Breaking Changes

All Users need to update to this version to prevent Security Issue (detailed in the link)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

[0dd]

@olaservo @cliffhall Please take a look on this critical fix.

[olaservo]

@0dd could you allow access to the doc? I just requested it with my google account.

[0dd]

@0dd could you allow access to the doc? I just requested it with my google account.

Thanks @olaservo added

[cliffhall]

I also requested access.

[0dd]

I also requested access.

Thanks @cliffhall added

[cliffhall]

LGTM! 👍

[0dd]

Since this is a security fix for the report, could we cut a patch release as the patched version: @modelcontextprotocol/server-memory@0.6.4? I didn’t bump the version in the PR. I assumed releases are handled in a separate commit and reviewed by the maintainer team.

We'll make a release out ASAP, it will change the server version to the dated release number.

[cliffhall]

Also, may you help open a GitHub Security Advisory and request a CVE for this issue? I’m a security researcher and would appreciate a CVE ID for attribution and tracking. For reference, I noticed the recent Server FileSystem advisories (e.g., CVE-2025-53110 and CVE-2025-53109) also managed by NPM. I previously submitted this via h1, but it wasn’t triaged. Could you help loop in the security team?

@jenn-newton

[0dd]

Hi team I saw this have been fixed in the version @modelcontextprotocol/server-memory@2025.9.25
Thank you all for the fix version build.

@jenn-newton @cliffhall Can you also help request the CVE for this one? I have also discussed the detailed threat model through discord.

The affected version was from npm version 0.2.0 till the date version <@2025.9.25