Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2022-4846

MEDIUM

CVE-2022-4846 is a medium-severity (CVSS 6.3) Cross-Site Request Forgery (CSRF) vulnerability in github.com/usememos/memos. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-4846 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Request Forgery (CSRF) in usememos/memos

Also known asGHSA-cwrm-33qq-4w2x
Published
Dec 29, 2022
Updated
Jul 15, 2026
Affected
1 pkg
Patched
None yet
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

Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/usememos/memosall versionsNo fix
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Remediation status

    No patched version of github.com/usememos/memos has shipped for CVE-2022-4846 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-4846 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 CVE-2022-4846. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1.
O3 Security · Impact-Aware SCA

Is CVE-2022-4846 in your dependencies?

O3 detects CVE-2022-4846 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.