# CVE-2026-115725: Chatwoot before 4.17.0 Cross-Account Authorization Bypass via source_id


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-8r78-9655-cv92

## What is CVE-2026-115725?

CVE-2026-115725 is a low-severity vulnerability in chatwoot, published on 23 Oct 2026. 

### Official description

Chatwoot before 4.17.0 contains an authorization bypass vulnerability that allows authenticated agent bots to access other accounts by supplying a foreign contact inbox source_id. Attackers can call the conversations create endpoint with another account's source_id to create or retrieve conversations and post messages to that account's contacts.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-115725 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115725 is a low-severity vulnerability in chatwoot, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115725 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-115725/ (Markdown: https://insights.sbomify.com/CVE-2026-115725/index.md)
```

## Sources

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

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