Is CVE-2026-63765 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63765 being exploited in the wild.

How severe is CVE-2026-63765?

High severity, with a CVSS score of 8.2, published 23 July 2026.

Is there a fix for CVE-2026-63765?

A patch was published on 2026-07-16: Fix merged into develop branch via PR #15039 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63765 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-63765?

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.

CVE-2026-63765: Chatwoot authentication bypass in conversation direct uploads

CVE-2026-63765 · Severity: high · CVSS 8.2 · Published 2026-07-23

Chatwoot, an open-source customer engagement platform, contained a security flaw that allowed unauthorized individuals to upload files to any customer account without logging in. An attacker could exploit this to store arbitrary data on the company's servers, potentially leading to storage exhaustion or the hosting of malicious content. This issue has been resolved in version 4.16.0.

Technologies: Chatwoot. Vendors: Chatwoot.

Quick answers

Is CVE-2026-63765 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63765 being exploited in the wild.
How severe is CVE-2026-63765?: High severity, with a CVSS score of 8.2, published 23 July 2026.
Which products and versions are affected?: Chatwoot < 4.16.0.
Is there a fix for CVE-2026-63765?: A patch was published on 2026-07-16: Fix merged into develop branch via PR #15039 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63765 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-63765?: 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

An authentication bypass exists in the `Api::V1::Accounts::Conversations::DirectUploadsController` because it inherited directly from `ActiveStorage::DirectUploadsController` without implementing the standard API authentication stack. Additionally, the `EnsureCurrentAccountHelper#ensure_current_account` helper failed to enforce membership checks when `current_user` was nil, allowing unauthenticated requests to proceed. A remote, unauthenticated attacker can exploit this by sending a POST request to the conversation direct uploads endpoint to obtain signed PUT URLs. This allows the attacker to write arbitrary data to the application's storage backend (e.g., S3, GCS, or local disk) across different tenant accounts. The vulnerability is fixed in version 4.16.0 by aligning the controller with standard account authentication and updating the account helper to return a 401 status for unauthenticated requests.

Affected products

Chatwoot Chatwoot < 4.16.0

Timeline

2026-06-13: disclosed: Initial report of the vulnerability
2026-07-16: patched: Fix merged into develop branch via PR #15039
2026-07-23: advisory: CVE-2026-63765 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.