# CVE-2026-44707: Chatwoot: Pre-Account Takeover via OAuth on Unconfirmed Accounts

> Attackers can pre-register unconfirmed accounts to hijack legitimate users via OAuth, gaining access to sensitive dashboard data and API keys.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-8qxm-4p4p-cfhm

## What is CVE-2026-44707?

CVE-2026-44707 is a medium-severity authentication bypass vulnerability in chatwoot, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Chatwoot is a customer engagement suite. From 2.14.0 to before 4.13.0, a Pre-Account Takeover (Pre-ATO) vulnerability existed in Chatwoot's authentication flow. Because email confirmation was not enforced before an account became usable, an attacker could pre-register an email address they did not own and set a password. If the legitimate owner of that email later signed in to Chatwoot using Google OAuth (or another OmniAuth provider), the OAuth flow silently confirmed the existing account without invalidating the attacker's pre-set credentials. The attacker could then continue to log in with the password they had originally chosen and access any data the victim subsequently entered into the dashboard, including PII, API keys, and other sensitive information. This vulnerability is fixed in 4.13.0.

Weakness: CWE-287 (Improper Authentication), CWE-283 (Unverified Ownership)

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


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

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

## Is CVE-2026-44707 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44707 is a medium-severity authentication bypass vulnerability in chatwoot, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44707 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-44707/ (Markdown: https://insights.sbomify.com/CVE-2026-44707/index.md)
```

## Sources

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

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