Mastra Memory API Thread Ownership Check Is a No-op When mapUserToResourceId Is Unset
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mastra-ai | mastra | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mastra-ai | Mastra |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.536% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mastra-ai
Mastra-ai mastra |
|
| Vendors & Products |
Mastra-ai
Mastra-ai mastra |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Mastra Memory API Thread Ownership Check Is a No-op When mapUserToResourceId Is Unset | |
| Weaknesses | CWE-862 | |
| References |
|
|
| Metrics |
cvssV3_1
|