Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-63765 – Authentication Bypass in Direct Uploads Controller – Chatwoot before 4.16.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-63765 is a high-severity authentication bypass (CWE-306: Missing Authentication for Critical Function) in Chatwoot, the open-source customer support and live-chat platform, affecting all versions prior to 4.16.0. Unauthenticated remote attackers can exploit a missing authentication check in the direct uploads controller to create arbitrary ActiveStorage blobs across any tenant account and obtain signed PUT URLs to write arbitrary data to the application’s storage backend. The CVSS v3.1 base score is 8.2 (HIGH).

Technical details

  • Root cause: The DirectUploadsController for conversations inherits from Rails’ ActiveStorage::DirectUploadsController instead of Chatwoot’s authenticated API base class. This architectural flaw causes the authenticate_user! before-action filter — present in Api::BaseController — to be entirely bypassed. The remaining authorization gate (EnsureCurrentAccountHelper#ensure_current_account) short-circuits on if current_user, which evaluates to nil for unauthenticated requests.
  • Affected endpoint: POST /api/v1/accounts/:account_id/conversations/:conversation_id/direct_uploads
  • Trigger conditions: Any unauthenticated HTTP request to the above endpoint with valid blob metadata is sufficient — no credentials, session, or user interaction required.
  • Attack flow: An attacker sends an unauthenticated POST with blob metadata; the controller resolves any account by ID and any conversation via its sequential display_id (a trivially guessable integer), then returns a signed, single-use PUT URL directly from Rails ActiveStorage.
  • Impact: Unauthenticated attackers can create storage blobs and stage arbitrary file content on the application’s configured storage backend (local disk, Amazon S3, Google Cloud Storage, etc.) across any tenant account in a multi-tenant deployment. This enables: storage exhaustion and denial of service via resource consumption; cross-tenant blob creation and database pollution; and attacker-controlled file staging on the application’s own storage domain prior to any authentication.

Affected software

  • Chatwoot — all versions before 4.16.0

Severity

  • CVSS v3.1 Base Score: 8.2 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade to Chatwoot v4.16.0 or later. The fix enforces authentication on the direct uploads controller by adding include AccessTokenAuthHelper and before_action :authenticate_user!, ensuring only authenticated agents with appropriate conversation access can initiate file uploads.
  • If immediate upgrade is not feasible: Restrict network-level access to the /api/v1/accounts/*/conversations/*/direct_uploads endpoint at the reverse proxy or WAF layer to authenticated session origins only. Monitor storage usage for unexpected blob creation activity.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge