dbcve.org
Rocket.chatApplication

CVE-2026-30833

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 7.10.8 / 7.11.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to versions 7.10.8, 7.11.5, 7.12.5, 7.13.4, 8.0.2, 8.1.1, and 8.2.0, a NoSQL injection vulnerability exists in Rocket.Chat's account service used in the ddp-streamer micro service that allows unauthenticated attackers to manipulate MongoDB queries during authentication. The vulnerability is located in the username-based login flow where user-supplied input is directly embedded into a MongoDB query selector without validation. An attacker can inject MongoDB operator expressions (e.g., { $regex: '.*' }) in place of a username string, causing the database query to match unintended user records. This issue has been patched in versions 7.10.8, 7.11.5, 7.12.5, 7.13.4, 8.0.2, 8.1.1, and 8.2.0.

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

A NoSQL injection vulnerability in Rocket.Chat's ddp-streamer microservice allows unauthenticated attackers to manipulate MongoDB queries during the username-based login flow by injecting MongoDB operator expressions (e.g., $regex) into the username field, enabling matching of unintended user records.

MitigationUpgrade to versions 7.10.8, 7.11.5, 7.12.5, 7.13.4, 8.0.2, 8.1.1, or 8.2.0 which contain the patch for proper input validation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rocket.chatApplication
Affected:< 7.10.8>= 7.11.0, < 7.11.5>= 7.12.0, < 7.12.5>= 7.13.0, < 7.13.4>= 8.0.0, < 8.0.2>= 8.1.0, < 8.1.1= 8.2.0

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Confirm Rocket.Chat is accessible
    Send an HTTP request to your Rocket.Chat server home page or check if port 3000 (or your configured port) is listening and responding
    Affected if The server is reachable and running Rocket.Chat software
  2. Identify the installed Rocket.Chat version
    Query the Rocket.Chat API endpoint /api/info or check the package.json/version file in the Rocket.Chat installation directory
    Affected if The returned version falls within any of these ranges: < 7.10.8; >= 7.11.0 and < 7.11.5; >= 7.12.0 and < 7.12.5; >= 7.13.0 and < 7.13.4; >= 8.0.0 and < 8.0.2; >= 8.1.0 and < 8.1.1; or equals 8.2.0
  3. Determine if the ddp-streamer microservice is deployed
    Inspect your deployment configuration (docker-compose.yml, Kubernetes manifests, or service inventory) for a ddp-streamer service component
    Affected if The ddp-streamer microservice is present in your deployment
  4. Verify username-based authentication is enabled
    Check the Rocket.Chat authentication settings in the admin panel under 'Login' section, or inspect the accounts configuration for Username login method
    Affected if Username/password authentication with direct username lookup is enabled as a login option

If Rocket.Chat is running with an affected version AND the ddp-streamer microservice is present AND username-based login is enabled, the environment is vulnerable to CVE-2026-30833.

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
Upgrade available Upgrade to 7.10.8 / 7.11.5 / 7.12.5 or later
Fixed in 7.10.87.11.57.12.5
Interim mitigation

Upgrade to versions 7.10.8, 7.11.5, 7.12.5, 7.13.4, 8.0.2, 8.1.1, or 8.2.0 which contain the patch for proper input validation.

Recommended fix High confidence

Upgrade to version 8.2.0 (or the latest 8.x stable release)

  1. 1. Back up your Rocket.Chat database and configuration files before proceeding
  2. 2. Identify your current Rocket.Chat version by checking the admin panel or running `rocketchatctl status` or checking the container/logs
  3. 3. If your current version is < 7.10.8: upgrade directly to 7.10.8 or later (recommended: 8.2.0)
  4. 4. If your current version is >= 7.11.0 and < 7.11.5: upgrade to 7.11.5 or later (recommended: 8.2.0)
  5. 5. If your current version is >= 7.12.0 and < 7.12.5: upgrade to 7.12.5 or later (recommended: 8.2.0)
  6. 6. If your current version is >= 7.13.0 and < 7.13.4: upgrade to 7.13.4 or later (recommended: 8.2.0)
  7. 7. Use your deployment method (Docker, snap, or manual) to perform the upgrade following the official Rocket.Chat upgrade documentation
  8. 8. Verify the upgrade was successful by checking the version in the admin panel
Caveat Review Rocket.Chat 8.x release notes for potential breaking changes before upgrading; major version upgrades may require migration steps

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

Fix this in Rocket.chat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30833 — 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-30833 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