# CVE-2024-29030: GO-2024-3046 - memos vulnerable to Server-Side Request Forgery in /api/resource in github.com/usememos/memos

Source: https://junglewise.ai/threats/cve-2024-29030-memos-vulnerable-to-server-side-request-forgery-in-api-resource  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-08-06  
License: CC BY 4.0 with a link back

CVE-2024-29030 · Severity: low · CVSS 3.1 · Published 2024-08-06

memos vulnerable to Server-Side Request Forgery in /api/resource in github.com/usememos/memos

Technologies: [github.com/usememos/memos (Go)](https://junglewise.ai/threats/technologies/github-com-usememos-memos). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2024-29030 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-29030 being exploited in the wild.

**How severe is CVE-2024-29030?** Low severity, with a CVSS score of 3.1, published 6 August 2024.

**Which products and versions are affected?** github.com/usememos/memos (Go) SEMVER:introduced=0,fixed=0.22.0.

**Is there a fix for CVE-2024-29030?** Yes. github.com/usememos/memos (Go): upgrade to 0.22.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-29030?** Check whether you run github.com/usememos/memos (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/usememos/memos (Go): upgrade to 0.22.0 or later

  ```sh
  go get github.com/usememos/memos@v0.22.0
  ```


## Affected products

- github.com/usememos/memos (Go) SEMVER:introduced=0,fixed=0.22.0

## Identifiers

- CVE-2024-29030
- GHSA-65fm-2jgr-j7qq
- GO-2024-3046

## Related threats

- [usememos Memos incorrect privilege assignment in UpdateInstanceSetting](https://junglewise.ai/threats/cve-2026-6634-usememos-memos-incorrect-privilege-assignment-in)
- [usememos memos path traversal in Attachment service](https://junglewise.ai/threats/cve-2025-65799-usememos-memos-path-traversal-in-attachment-service)
- [usememos memos broken access control in Identity Provider service](https://junglewise.ai/threats/cve-2025-65797-usememos-memos-broken-access-control-in-identity-provider-service)
- [usememos memos incorrect access control in user registration API](https://junglewise.ai/threats/cve-2025-65795-usememos-memos-incorrect-access-control-in-user-registration-api)
- [usememos memos incorrect access control in attachments](https://junglewise.ai/threats/cve-2025-65798-usememos-memos-incorrect-access-control-in-attachments)