# CVE-2026-57947: Pinpoint - Server-Side Request Forgery via Alarm Webhook Registration

> Authenticated attackers can exploit missing SSRF protection in Pinpoint's webhook registration to access internal network resources and metadata endpoints.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA: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:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-xx75-4fhf-jf2w

## What is CVE-2026-57947?

CVE-2026-57947 is a medium-severity server-side request forgery vulnerability in pinpoint-apm pinpoint, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pinpoint through 3.1.0 contains a server-side request forgery vulnerability in the webhook registration endpoint that allows authenticated users to register internal URLs due to missing SSRF protection. Attackers can trigger alarm threshold breaches to force the server to issue POST requests to internal hosts and metadata endpoints, enabling unauthorized access to internal network resources.

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

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


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

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

## Is CVE-2026-57947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57947 is a medium-severity server-side request forgery vulnerability in pinpoint-apm pinpoint, published on 29 Jun 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-57947 in the wild and no public exploit code.

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

## Sources

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

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