Quick answers
- Is CVE-2026-92527 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92527 being exploited in the wild.
- How severe is CVE-2026-92527?
- Medium severity, with a CVSS score of 6.3, published 16 September 2026.
- Which products and versions are affected?
- Chatwoot up to 4.17.1.
- Is there a fix for CVE-2026-92527?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92527 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92527?
- Check whether you run Chatwoot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the callbacks_controller.rb file where the Shopify OAuth callback endpoint constructs an OAuth2::Client using unsanitized user input (params[:shop]) as the site hostname without validation. When the OAuth2 gem exchanges an authorization code, it performs a POST request containing client_id and client_secret to an attacker-controlled host instead of the legitimate Shopify endpoint. An authenticated agent-level user can obtain a non-expiring state JWT (lacking expiration time and shop binding) and replay it with an arbitrary shop parameter, triggering the SSRF condition. The attack requires prior authentication to the Chatwoot instance and knowledge of valid Shopify app credentials configured in the system.
Affected products
- Chatwoot Chatwoot up to 4.17.1
Timeline
- 2026-09-16: disclosed
- other: Security issue reported 2026-05-11 with no vendor response