Quick answers
- Is CVE-2026-32994 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32994 being exploited in the wild.
- How severe is CVE-2026-32994?
- Medium severity, with a CVSS score of 5.3, published 19 May 2026.
- Which products and versions are affected?
- Rocket.Chat <8.5.0, <8.4.2, <8.3.4, <8.2.4, <8.1.5, <8.0.6, <7.13.8, <7.10.12.
- Is there a fix for CVE-2026-32994?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-32994 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32994?
- Check whether you run Rocket.Chat 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
The vulnerability exists in the `/api/v1/autotranslate.translateMessage` endpoint due to a lack of authorization checks. The endpoint uses `Messages.findOneById(messageId)` to fetch message data but fails to invoke `canAccessRoomIdAsync` or any equivalent room access validation. An authenticated attacker can exploit this by supplying a target `messageId` to the endpoint, which returns the complete `IMessage` object. This object includes sensitive fields such as the message text, sender information, room ID, timestamps, and markdown content, regardless of whether the user is a member of the room where the message originated.
Affected products
- Rocket.Chat Rocket.Chat <8.5.0, <8.4.2, <8.3.4, <8.2.4, <8.1.5, <8.0.6, <7.13.8, <7.10.12
Timeline
- 2026-05-19: disclosed: CVE published to NVD via HackerOne report