Is CVE-2025-65797 exploited in the wild?

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

How severe is CVE-2025-65797?

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

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

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

Am I affected by CVE-2025-65797?

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-65797: usememos memos broken access control in Identity Provider service

CVE-2025-65797 · Severity: medium · CVSS 6.5 · Published 2025-12-08

A vulnerability in Memos, a self-hosted note-taking application, allows users with low-level access to modify or delete the system's identity provider settings. This could allow an attacker to lock other users out of the system or redirect login processes to a malicious server to take over administrator accounts. The flaw compromises the integrity of the authentication process and can lead to a total loss of access for legitimate users.

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

Quick answers

Is CVE-2025-65797 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-65797 being exploited in the wild.
How severe is CVE-2025-65797?: Medium severity, with a CVSS score of 6.5, 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-65797?: 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-65797 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2025-65797?: 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/CWE-284) exists in the Identity Provider (IDP) service of Memos v0.25.2. The application fails to restrict administrative operations on the `/api/v1/identityProviders` endpoint to host/admin users. Authenticated attackers with low-level privileges can send PATCH or DELETE requests to modify or remove OAuth/SSO configurations. Additionally, the client secret for configured IDPs is exposed to unauthenticated users via GET requests. By modifying the IDP configuration to point to a malicious server, an attacker can facilitate account takeover of any user, including the host. The issue was addressed in version 0.25.3 by adding missing authorization checks.

Affected products

usememos memos 0.25.2

Identifiers

CVE-2025-65797
GHSA-99m2-qwx6-2w6f
GO-2025-4220

Timeline

2025-11-03: other: 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: Researcher advisory published by usd HeroLab
2025-12-08: disclosed: CVE published to NVD

References

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