# CVE-2026-72606: Pinry Pinry - Server-Side Request Forgery

> Unauthenticated attackers can force the Pinry server to make arbitrary HTTP requests, potentially accessing internal services or cloud metadata.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-x8h5-cpr3-h43m

## What is CVE-2026-72606?

CVE-2026-72606 is a high-severity server-side request forgery vulnerability in Pinry, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A server-side request forgery vulnerability in Pinry through 2.1.13 allows unauthenticated remote attackers to make the server issue HTTP requests to arbitrary internal or external hosts via the pin-from-URL feature. The feature passes the user-supplied URL directly to requests.get() without host or IP validation, and ALLOW_NEW_REGISTRATIONS defaults to true enabling anonymous triggering. An attacker can reach internal services or cloud metadata endpoints from the server.

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

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


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

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

## Is CVE-2026-72606 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72606 is a high-severity server-side request forgery vulnerability in Pinry, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72606 in the wild and no public exploit code.

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

## Sources

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

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