Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Mnemosyne (PyPI package mnemosyne-memory) versions before 3.10.1 have a sync server whose authentication check did not verify JWT signatures, so any well-formed token was accepted. A network-reachable attacker with no credentials can impersonate any user and read or modify that user's sync data. Upgrade to mnemosyne-memory 3.10.1; as a workaround, restrict network access to the sync server to trusted clients.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.1 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0032, the 25th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:09 UTC First seen by agentprime
- 31 Oct 2026, 14:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-xcw4-53cc-hv32
- OSV: GHSA-xcw4-53cc-hv32
- github.com/AxDSan/mnemosyne/security/advisories/GHSA-xcw4-53cc-hv32
- github.com/mnemosyne-oss/mnemosyne/pull/373
- github.com/mnemosyne-oss/mnemosyne/commit/a0b6b8711a1a485304971710dc3571e29ff9dbeb
- github.com/AxDSan/mnemosyne
- github.com/mnemosyne-oss/mnemosyne/releases/tag/v3.10.1