# Memos Server-Side Request Forgery (SSRF) in github.com/usememos/memos

Advisory record · `GHSA-wfxg-v3j4-7qmj`

- **Identifiers:** `GHSA-wfxg-v3j4-7qmj` · `CVE-2025-22952` · `GO-2025-3492`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 3 Mar 2025
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Mar 2025, 19:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/usememos/memos` (Go): affected `all versions`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Go package github.com/usememos/memos is affected in all versions, and the source lists no fixed version. The source gives few details about the attack path, beyond describing it as a server-side request forgery that carries a CVSS 3.1 base score of 9.8. No fix is listed, so check the project for updates or restrict access to the server until one is available.

Written 10 Nov 2026.

## 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

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.029, the 87th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 3 Mar 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-wfxg-v3j4-7qmj](https://github.com/advisories/GHSA-wfxg-v3j4-7qmj)
- [OSV: GHSA-wfxg-v3j4-7qmj](https://osv.dev/vulnerability/GHSA-wfxg-v3j4-7qmj)
- <https://github.com/advisories/GHSA-wfxg-v3j4-7qmj>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-22952>
- <https://github.com/usememos/memos/commit/f17774cb3b9612495d89576a91ab3480018cb0b6>
- <https://github.com/usememos/memos/commit/f8c973c938742827baaf6665cfe66805dc8e8d02>
- <https://github.com/usememos/memos/pull/4421>
- <https://github.com/usememos/memos/pull/4428>
- <https://elest.io/open-source/memos>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wfxg-v3j4-7qmj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wfxg-v3j4-7qmj/>. Everything for agents: <https://agentprime.io/llms.txt>.
