# CVE-2026-5205: chatwoot Webhook API trigger.rb Trigger server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the Chatwoot webhook API to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 31 Mar 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-rphr-fw27-85gg

## What is CVE-2026-5205?

CVE-2026-5205 is a medium-severity server-side request forgery vulnerability in chatwoot, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in chatwoot up to 4.11.2. Affected by this vulnerability is the function Webhooks::Trigger in the library lib/webhooks/trigger.rb of the component Webhook API. Such manipulation of the argument url leads to server-side request forgery. The attack can be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-5205 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5205 is a medium-severity server-side request forgery vulnerability in chatwoot, published on 31 Mar 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-5205 in the wild and no public exploit code.

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

## Sources

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

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