CVE-2026-65644: XSS

Published Aug 21, 2026
·
Updated

Rocket.Chat in versions before 8.8.0, 8.7.1, 8.6.2, 8.5.3, 8.4.6, 8.3.8, 8.2.8, 8.1.8, and 7.10.15 has a REST API endpoint POST /api/v1/livechat/visitor that accepts an unauthenticated, unsanitized name field for Livechat visitors. This name is stored raw and later rendered via dangerouslySetInnerHTML in the Omnichannel Queue side panel (InquireSidePanelItem.tsx), injecting a real, clickable HTML link - pointing to any attacker-controlled domain, with arbitrary social-engineering text - into the DOM of any agent viewing the queue.

Affected Software

1 affected component
Rocket.Chat Rocket.Chat<8.8.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.8.0
  2. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.7.1
  3. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.6.2
  4. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.5.3
  5. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.4.6
  6. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.3.8
  7. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.2.8
  8. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 8.1.8
  9. Upgrade

    Upgrade Rocket.Chat to a version that resolves this vulnerability.

    Fixed in 7.10.15

Event History

Aug 21, 2026
CVE Published
via MITRE·02:53 AM
Data Sourced
via MITRE·02:53 AM
DescriptionWeakness

Frequently Asked Questions

1

Who is exposed to the injected content?

Any agent who views the Omnichannel Queue side panel can be shown the attacker-controlled clickable link. The issue affects deployments using Livechat and the affected queue interface.

2

What does an attacker need to exploit this?

The attacker only needs to submit a POST request to /api/v1/livechat/visitor with a crafted name value. The endpoint accepts this field without authentication.

3

Is user interaction required for impact?

An agent must view the relevant queue item for the crafted HTML link to be rendered. The link can contain attacker-chosen social-engineering text and point to an attacker-controlled domain.

4

What versions should be updated?

Update to 8.8.0, 8.7.1, 8.6.2, 8.5.3, 8.4.6, 8.3.8, 8.2.8, 8.1.8, or 7.10.15, as applicable to the release branch in use.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203