Security
How to report a vulnerability, what we support, and why the default deployment keeps data local.
Report privately
Please do not open a public issue for a security problem. Use GitHub's private vulnerability reporting on the MemOS repository, or email the maintainer through the address on their GitHub profile. Include reproduction steps, affected versions, and impact.
Open a private advisorySupported versions
| Version | Supported |
|---|---|
| 1.x (latest) | Yes |
| < 1.0.0 | No |
Response targets
Security design
Local by default
The SDK, CLI, and MCP server read and write a SQLite file on your machine. Core memory operations make no network calls and require no API key.
Loopback HTTP
The optional HTTP surface binds 127.0.0.1 unless you explicitly pass another host. Setting MEMOS_API_KEY enforces a bearer token on every route except /health, /docs, /redoc, and /openapi.json.
No telemetry
There is no phone-home path. Token-savings counters are in-process and reset when the process exits.
Auditable storage
Memories, supersede history, and provenance links live in an ordinary SQLite database you can inspect with any client. The full source is MIT licensed.
Scope
In scope: the MemOS SDK, CLI, MCP server, Python HTTP server, plugin hooks, and the Universal MCP Toolkit. Out of scope: issues that require an already-compromised machine or unsupported versions, and reports produced solely by automated scanners without a demonstrated impact.
We will not pursue legal action against researchers who act in good faith, avoid privacy violations and data destruction, and give us reasonable time to fix the issue before disclosure.