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.
CVE-2026-92527
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-09-16. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026GitHub - chatwoot/chatwoot: Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬 · GitHub
https://github.com/chatwoot/chatwoot/[Security] Chatwoot Shopify OAuth SSRF + Credential Exfiltration · Issue #14887 · chatwoot/chatwoot · GitHub
https://github.com/chatwoot/chatwoot/issues/14887Vendor Advisories for CVE-2026-92527(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-21 02:15 UTCEG score recompute
- 2026-09-21 02:15 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 00:37 UTCEG score recompute
- 2026-09-20 00:37 UTCGHSA enrichment
- 2026-09-18 22:59 UTCEG score recompute
- 2026-09-18 22:59 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 21:22 UTCEG score recompute
- 2026-09-17 21:22 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 14:21 UTCNVD updateCVSS v4 → 2.1
- 2026-09-17 14:19 UTCEG score recompute
- 2026-09-17 14:19 UTCGHSA enrichment
- 2026-09-17 14:19 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-09-16 21:27 UTCEG score recompute
- 2026-09-16 21:22 UTCNVD updateCVSS v4 → 2.1
- 2026-09-16 20:34 UTCEG score recompute
- 2026-09-16 20:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-92527?
When was CVE-2026-92527 disclosed?
Is CVE-2026-92527 actively exploited?
What is the CVSS score of CVE-2026-92527?
How do I remediate CVE-2026-92527?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92527
Is Your Infrastructure Affected by CVE-2026-92527?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.