CVE-2022-4686 json
Authorization Bypass Through User-Controlled Key in usememos/memos
published 2022-12-23 3 y ago modified 2026-06-17 4 mo ago also GHSA-68gw-r2x5-7r5r , GO-2022-1215 , EUVD-2022-7526
- cvss
- 8.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.0.
Patch / fix
- go github.com/usememos/memos 0.9.0
- usememos usememos/memos 0.9.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/caa0b22c-501f-44eb-af65-65c315cd1637 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.6 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/usememos/memos | <0.9.0 |
0.9.0 |
Affected products
- usememos usememos/memos
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/usememos/memos/commit/dca35bde877aab6e64ef51b52e590b5d48f692f9
web, patch, third-party-advisory
-
huntr.dev
/bounties/caa0b22c-501f-44eb-af65-65c315cd1637
web, exploit, issue-tracking, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-4686
advisory
-
github.com
/usememos/memos
package
-
github.com
/advisories/GHSA-68gw-r2x5-7r5r
advisory
Sources
- CVE List CVE-2022-4686
- GitHub Advisory GHSA-68gw-r2x5-7r5r
- NVD CVE-2022-4686
- OSV GO-2022-1215
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.