# CVE-2026-92527: chatwoot Shopify OAuth callbacks_controller.rb server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in Chatwoot's Shopify OAuth callback controller 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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-ph4j-4h7p-2fmv, GHSA-wxhm-4rjw-9m7v

## What is CVE-2026-92527?

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

### Official description

A vulnerability has been found in chatwoot up to 4.17.1. This impacts an unknown function of the file callbacks_controller.rb of the component Shopify OAuth. The manipulation leads to server-side request forgery. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-92527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92527 is a medium-severity server-side request forgery vulnerability in chatwoot, published on 16 Sep 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-92527 exists.

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

## Sources

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

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