Is github.com/usememos/memos 0.31 vulnerable?
Go · 1 release from 0.31.0 to 0.31.0 · latest github.com/usememos/memos is 0.31.0 · checked 18 Nov 2026
Yes: 6 known advisories
Yes. github.com/usememos/memos 0.31.0, the last 0.31 release, is affected by 6 known security advisories (1 high, 5 low), including CVE-2023-4698, CVE-2026-6634, CVE-2024-21635. At least one has no fixed release yet.
Is your project on an affected github.com/usememos/memos?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/usememos/memos 0.31.0
Memos has an Incorrect Privilege Assignment issue in github.com/usememos/memos
- Affected
- All versions
- Fixed in
- No fix released
Memos' Access Tokens Stay Valid after User Password Change in github.com/usememos/memos
- Affected
- All versions
- Fixed in
- No fix released
Memos Vulnerable to Path Traversal via the CreateResource Endpoint in github.com/usememos/memos
- Affected
- All versions
- Fixed in
- No fix released
Memos Vulnerable to Stored Cross-Site Scripting in github.com/usememos/memos
- Affected
- All versions
- Fixed in
- No fix released
Memos Server-Side Request Forgery (SSRF) in github.com/usememos/memos
- Affected
- All versions
- Fixed in
- No fix released
usememos/memos vulnerable to improper input validation
- Affected
- All versions
- Fixed in
- No fix released
Which of your client projects are still on github.com/usememos/memos 0.31?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/usememos/memos version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/usememos/memos versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.