# CVE-2026-82476: Memos through 0.30.0 SSRF via Omitted CGNAT Address Range

> Unauthenticated attackers can bypass SSRF protections to access internal cloud metadata services and read sensitive data via the link-metadata fetcher.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-rw55-gcm9-cgjp

## What is CVE-2026-82476?

CVE-2026-82476 is a medium-severity server-side request forgery vulnerability in usememos memos, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memos through 0.30.0 omits the 100.64.0.0/10 carrier-grade NAT address range from SSRF protection in its link-metadata fetcher, allowing unauthenticated attackers to bypass IP validation. Attackers can make the server request internal hosts in that range including cloud metadata services and read page titles and descriptions back.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-82476?


## How do I fix CVE-2026-82476?

No fix has been published for CVE-2026-82476 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82476 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82476 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82476 and fix it if it is affected.

What it is: CVE-2026-82476 is a medium-severity server-side request forgery vulnerability in usememos memos, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82476 exists.

Affected product: usememos memos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82476/ (Markdown: https://insights.sbomify.com/CVE-2026-82476/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82476
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82476
- OSV: https://osv.dev/vulnerability/CVE-2026-82476

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82476/
Summaries are generated and may contain mistakes; the official description above is the record.