How severe is GHSA-ghx2-6v4g-9wmm?

GHSA-ghx2-6v4g-9wmm has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-ghx2-6v4g-9wmm?

GHSA-ghx2-6v4g-9wmm affects the following packages: github.com/usememos/memos (Go). Ecosystems affected: Go.

How do I fix GHSA-ghx2-6v4g-9wmm?

Update github.com/usememos/memos to 0.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghx2-6v4g-9wmm is resolved across your whole dependency graph.

How do I detect GHSA-ghx2-6v4g-9wmm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-ghx2-6v4g-9wmm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-ghx2-6v4g-9wmm?

O3 pinpoints whether GHSA-ghx2-6v4g-9wmm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-ghx2-6v4g-9wmm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-ghx2-6v4g-9wmm, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-ghx2-6v4g-9wmm?

GHSA-ghx2-6v4g-9wmm is classified as CWE-648 (CWE-648). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-ghx2-6v4g-9wmm?

6 Metasploit modules reference GHSA-ghx2-6v4g-9wmm, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-ghx2-6v4g-9wmm published, and has it been updated?

GHSA-ghx2-6v4g-9wmm was published on December 28, 2022 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-ghx2-6v4g-9wmm

HIGH

GHSA-ghx2-6v4g-9wmm is a high-severity (CVSS 8.1) CWE-648 vulnerability in github.com/usememos/memos. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-ghx2-6v4g-9wmm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

usememos/memos makes Incorrect Use of Privileged APIs

Also known asCVE-2022-4796GO-2022-1236

Published

Dec 28, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

🐹github.com/usememos/memos

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

In usememos/memos 0.9.0 and prior, a user with login permission can delete all notes of the whole application via API DELETE https://demo.usememos.com/api/memo/$idnote. The vulnerability will lose all user notes data throughout the system, causing damage to user data.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/usememos/memos`	all versions	0.9.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Incorrect Use of Privileged APIs in GitHub repository usememos/memos pri…

huntr.devNVDJan 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/usememos/memos to 0.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghx2-6v4g-9wmm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-ghx2-6v4g-9wmm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-ghx2-6v4g-9wmm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In usememos/memos 0.9.0 and prior, a user with login permission can delete all notes of the whole application via `API DELETE https://demo.usememos.com/api/memo/$idnote`. The vulnerability will lose all user notes data throughout the system, causing damage to user data.

O3 Security · Impact-Aware SCA

Is GHSA-ghx2-6v4g-9wmm in your dependencies?

O3 detects GHSA-ghx2-6v4g-9wmm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works