Is CVE-2025-65796 exploited in the wild?

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

How severe is CVE-2025-65796?

Medium severity, with a CVSS score of 4.3, 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-65796?

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-65796 attacked?

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

Am I affected by CVE-2025-65796?

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-65796: usememos memos incorrect access control in Reaction service

CVE-2025-65796 · Severity: medium · CVSS 4.3 · Published 2025-12-08

Memos is a self-hosted note-taking application used for personal knowledge management and daily logs. A security flaw in the application's reaction system allows any logged-in user to delete reactions (such as emojis or likes) posted by other users on any memo. While this does not expose private note content, it allows malicious users to tamper with social interactions and engagement data within the platform.

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

Quick answers

Is CVE-2025-65796 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-65796 being exploited in the wild.
How severe is CVE-2025-65796?: Medium severity, with a CVSS score of 4.3, 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-65796?: 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-65796 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2025-65796?: 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-284/CWE-862) exists in the Reaction service of Memos v0.25.2. The application fails to validate if the user requesting the deletion of a reaction is the actual owner of that reaction. An authenticated attacker can exploit this by sending a DELETE request to the `/api/v1/reactions/<NumericIdOfReaction>` endpoint. By supplying the ID of a reaction belonging to another user, the attacker can successfully remove it from the system. The issue was addressed in pull request #5217 by adding owner-check authorization logic and was officially fixed in version 0.25.3.

Affected products

usememos memos 0.25.2

Identifiers

CVE-2025-65796
GHSA-8jcj-g9f4-qx42
GO-2025-4215

Timeline

2025-11-03: disclosed: First contact with vendor
2025-11-04: patched: Pull request submitted
2025-11-06: patched: Commit merged to main branch
2025-11-25: patched: Version 0.25.3 released
2025-12-03: advisory: Third-party advisory published by usd HeroLab
2025-12-08: advisory: NVD advisory published

References

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