Mastra Memory API Thread Ownership Check Is a No-op When mapUserToResourceId Is Unset
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
Mastra through 1.63.0 contains an authentication bypass vulnerability in the memory API thread ownership validation when mapUserToResourceId callback is omitted from configuration. Authenticated attackers can enumerate all threads via GET /api/memory/threads and read conversation history and metadata of other resource owners.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-82273
- 2026-10-03 Alias added: GHSA-q48c-g8g8-2xq8
More mastra-ai vulnerabilities
- TI-2025-38116 Mastra Docs MCP Server `@mastra/mcp-docs-server` Leads to Information Exposure CVSS 3.1MEDIUM 6.5
Sources
- CVE-2026-82273 · CVE Program
- CVE-2026-82273 · NVD
- FIRST EPSS
- GHSA-q48c-g8g8-2xq8 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences