# CVE-2026-72597: Friendica Friendica - Server-Side Request Forgery

> Authenticated users can exploit a link-preview endpoint to perform server-side request forgery, enabling internal network scanning and access to cloud metadata services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-mhpc-8ghx-95cq

## What is CVE-2026-72597?

CVE-2026-72597 is a medium-severity server-side request forgery vulnerability in Friendica, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A server-side request forgery vulnerability in Friendica through the 2026.08-dev branch allows authenticated users with a free self-registered account to probe internal network services via the link-preview endpoint. The endpoint fetches any user-supplied URL without applying an internal IP deny list. An attacker can use this to scan the internal network or access cloud metadata services.

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

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


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

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

## Is CVE-2026-72597 being exploited?

There is no known exploitation of CVE-2026-72597 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72597 is a medium-severity server-side request forgery vulnerability in Friendica, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72597 in the wild and no public exploit code.

Affected product: Friendica. 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-72597/ (Markdown: https://insights.sbomify.com/CVE-2026-72597/index.md)
```

## Sources

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

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