# CVE-2026-56227: Capgo - Server-Side Request Forgery via Webhook URL Validation

> Capgo allows admins to configure webhooks targeting internal addresses, enabling Server-Side Request Forgery and information disclosure.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **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:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-383x-vh5q-x2q9, GHSA-48hc-53hv-6x3f

## What is CVE-2026-56227?

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

### Official description

Capgo before 12.128.2 contains a server-side request forgery vulnerability in webhook URL validation that allows loopback and internal addresses. Organization admins can configure webhooks pointing to localhost or 127.0.0.1, and when triggered, the backend performs outbound requests to these addresses with error responses disclosed to users.

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

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


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

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

## Is CVE-2026-56227 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56227 is a medium-severity server-side request forgery vulnerability in Capgo, published on 20 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56227 exists.

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

## Sources

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

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