dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-32994

MEDIUM · 5.3 CVSS v3.0 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The /api/v1/autotranslate.translateMessage endpoint in versions <8.5.0, <8.4.2, <8.3.4, <8.2.4, <8.1.5, <8.0.6, <7.13.8, and <7.10.12 allows any authenticated user to retrieve the full content of any message from any room (private groups, direct messages, channels) by simply providing the target message ID. The endpoint fetches the message via Messages.findOneById(messageId) with no room access check (canAccessRoomIdAsync is never called), returning the complete IMessage object including message text, sender info, room ID, timestamps, and markdown content.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /api/v1/autotranslate.translateMessage endpoint in Rocket.Chat lacks room access validation, allowing any authenticated user to retrieve the full content of any message by providing its ID. The endpoint calls Messages.findOneById() without checking canAccessRoomIdAsync, exposing private messages, direct messages, and channel messages to unauthorized users.

MitigationImplement proper room access verification by calling canAccessRoomIdAsync (or equivalent authorization check) before returning message content to ensure users can only access messages from rooms they are authorized to view.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Rocket.Chat version
    Locate the version file or check the admin panel at /admin/info, or query the API endpoint /api/v1/info
    Affected if Version is earlier than 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, or 7.10.12 (any version before the fixes)
  2. Verify autotranslate module is enabled
    Navigate to Administration > Settings > AutoTranslate (or equivalent) in the Rocket.Chat admin panel, or inspect the configuration database for autotranslate settings
    Affected if The autotranslate feature is enabled and the version is vulnerable
  3. Confirm user is logged in with standard user account
    Log into Rocket.Chat with any regular user account (non-admin, no special room permissions)
    Affected if You have valid credentials for any user account in the system
  4. Test the vulnerable API endpoint with a cross-room message ID
    Send a POST request to /api/v1/autotranslate.translateMessage with a message ID from a room the authenticated user is NOT a member of. Include a valid auth token. Example: {"messageId":"<any-message-id>","targetLanguage":"en"}
    Affected if The API returns full message content (including sender, room ID, timestamps) for a message the user should not have access to, indicating the IDOR is present

You are affected if your Rocket.Chat version is before the fixed versions AND the autotranslate module is enabled, allowing any authenticated user to retrieve messages from rooms they do not belong to.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper room access verification by calling canAccessRoomIdAsync (or equivalent authorization check) before returning message content to ensure users can only access messages from rooms they are authorized to view.

Recommended fix Moderate confidence

Upgrade to Rocket.Chat 8.5.0 or later (for 8.x users), or 7.13.8/7.10.12 or later (for 7.x users)

  1. 1. Identify your current Rocket.Chat version by checking the admin panel or running `rocketctl version`
  2. 2. Determine which major version branch you are on (8.x or 7.x) to select the appropriate upgrade target
  3. 3. For 8.x users: Upgrade to version 8.5.0 or later
  4. 4. For 7.x users: Upgrade to version 7.13.8 or later if on 7.13 branch, or 7.10.12 or later if on 7.10 branch
  5. 5. Review the changelog/release notes for your target version to confirm the security fix is included
  6. 6. Perform a backup of your database before upgrading
  7. 7. Test the upgrade in a staging environment first
  8. 8. Apply the upgrade following standard Rocket.Chat upgrade procedures
Caveat Major version upgrades (7.x to 8.x) may include breaking changes; review upgrade documentation for database migrations and API compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32994 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data