Is CVE-2025-65798 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-65798 being exploited in the wild.

How severe is CVE-2025-65798?

Medium severity, with a CVSS score of 5.4, published 8 December 2025.

Which products and versions are affected?

github.com/usememos/memos (Go) SEMVER:introduced=0,fixed=0.25.3; Usememos Memos 0.25.2.

Is there a fix for CVE-2025-65798?

Yes. github.com/usememos/memos (Go): upgrade to 0.25.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-65798 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2025-65798?

Check whether you run github.com/usememos/memos (Go) or Usememos Memos 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.

CVE-2025-65798: usememos memos incorrect access control in attachments

CVE-2025-65798 · Severity: medium · CVSS 5.4 · Published 2025-12-08

A vulnerability in the Memos note-taking application allows users with low-level account access to modify or delete file attachments belonging to other users. This could lead to the unauthorized deletion of data from the server or the exposure of private attachments by making them public. The issue affects organizations or individuals using the self-hosted platform for private knowledge management and daily logging.

Technologies: github.com/usememos/memos (Go), Usememos Memos. Vendors: Go, Usememos.

Quick answers

Is CVE-2025-65798 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-65798 being exploited in the wild.
How severe is CVE-2025-65798?: Medium severity, with a CVSS score of 5.4, published 8 December 2025.
Which products and versions are affected?: github.com/usememos/memos (Go) SEMVER:introduced=0,fixed=0.25.3; Usememos Memos 0.25.2.
Is there a fix for CVE-2025-65798?: Yes. github.com/usememos/memos (Go): upgrade to 0.25.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-65798 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2025-65798?: Check whether you run github.com/usememos/memos (Go) or Usememos Memos 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.25.3 or later
```
go get github.com/usememos/memos@v0.25.3
```

Technical details

A broken access control vulnerability (CWE-862) exists in the Memo Attachment service of usememos memos v0.25.2. The application fails to validate the ownership of a memo or its associated attachments when processing update requests via the gRPC-Gateway REST API. An authenticated attacker can send a crafted PATCH request to the `/api/v1/memos/{memo_id}/attachments` endpoint to reassign arbitrary attachment IDs to their own memos or remove them entirely. Unassigning an attachment triggers its deletion from the server's disk, while reassigning a private attachment to a public memo makes the file accessible to others. The vulnerability was addressed in version 0.25.3 by adding proper authorization checks to the attachment and relation services.

Affected products

usememos memos 0.25.2

Identifiers

CVE-2025-65798
GHSA-8p44-g572-557h
GO-2025-4216

Timeline

2025-11-03: disclosed: First contact with vendor
2025-11-04: other: Pull request submitted
2025-11-06: patched: Fix merged to main branch
2025-11-25: other: Version 0.25.3 released
2025-12-03: advisory: Security advisory published by usd HeroLab

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.