Quick answers
- Is CVE-2026-44707 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44707 being exploited in the wild.
- How severe is CVE-2026-44707?
- Medium severity, with a CVSS score of 6.8, published 26 May 2026.
- Which products and versions are affected?
- Chatwoot >= 2.14.0, < 4.13.0.
- Is there a fix for CVE-2026-44707?
- A patch was published on 2026-04-02: Fix merged into develop branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44707 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44707?
- 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
A Pre-Account Takeover (Pre-ATO) vulnerability exists in Chatwoot's authentication flow due to improper verification of email ownership during the registration and OAuth linking process. An attacker can register an account using a victim's email address and set a password without completing email confirmation. When the legitimate owner later signs in using an OmniAuth provider (like Google), the system silently confirms the existing account but fails to invalidate the attacker's previously set password. This allows the attacker to continue accessing the account using their credentials even after the victim has populated it with sensitive data. The vulnerability is fixed in version 4.13.0 by rotating the stored password to a random value whenever an unconfirmed user completes an OAuth sign-in.
Affected products
- Chatwoot Chatwoot >= 2.14.0, < 4.13.0
Timeline
- 2026-03-23: other: Fix pull request submitted
- 2026-04-02: patched: Fix merged into develop branch
- 2026-05-05: advisory: GitHub Security Advisory published
- 2026-05-26: disclosed: CVE published to NVD