CVE-2026-30831
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 · uneditedRocket.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, authentication vulnerabilities exist in Rocket.Chat's enterprise DDP Streamer service. The Account.login method exposed through the DDP Streamer does not enforce Two-Factor Authentication (2FA) or validate user account status (deactivated users can still login), despite these checks being mandatory in the standard Meteor login flow. 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 confidenceRocket.Chat's enterprise DDP Streamer service contains authentication bypass vulnerabilities where the Account.login method fails to enforce Two-Factor Authentication (2FA) and does not validate user account status, allowing deactivated users to authenticate and bypassing mandatory 2FA checks that are enforced in the standard Meteor login flow.
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< 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.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Rocket.Chat versionRun `rocketchatctl version` or check the package.json file in the Rocket.Chat installation directory, or query the API endpoint `/api/info`Affected if The installed version falls within: < 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
-
Verify DDP Streamer service is enabledCheck the Rocket.Chat configuration for the DDP Streamer enterprise module - look for settings related to 'streamer' or 'ddp' in the admin panel under Enterprise > DDP Streamer, or check if the package is loaded in the running instanceAffected if The DDP Streamer service is enabled and the version is in the affected range
-
Confirm 2FA enforcement configurationReview the Rocket.Chat admin settings for Two-Factor Authentication - check if mandatory 2FA is enabled for users under Administration > Settings > Accounts > Two Factor AuthenticationAffected if 2FA is configured as mandatory or optional and the DDP Streamer is in use with an affected version
-
Test authentication via DDP Streamer endpointAttempt to authenticate using the Account.login method through the DDP Streamer endpoint (typically at /websocket with the DDP protocol) with a deactivated user account or with 2FA disabled when it should be requiredAffected if Authentication succeeds with a deactivated user account or bypasses 2FA when it should be enforced in the standard Meteor login flow
You are affected if Rocket.Chat is running a version in the affected range AND the DDP Streamer enterprise service is enabled, allowing authentication bypass for deactivated users or 2FA enforcement.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.10.87.11.57.12.5
Upgrade Rocket.Chat to versions 7.10.8, 7.11.5, 7.12.5, 7.13.4, 8.0.2, 8.1.1, or 8.2.0 or later to patch the DDP Streamer authentication bypass vulnerabilities.
Upgrade to 7.13.4 (for 7.x line) or 8.2.0 (latest stable)
- 1. Identify the currently installed Rocket.Chat version by checking the admin panel or running `rocketchat --version`
- 2. If running a version < 7.10.8: upgrade to version 7.10.8
- 3. If running version >= 7.11.0 and < 7.11.5: upgrade to version 7.11.5
- 4. If running version >= 7.12.0 and < 7.12.5: upgrade to version 7.12.5
- 5. If running version >= 7.13.0 and < 7.13.4: upgrade to version 7.13.4
- 6. Alternatively, upgrade to version 8.0.2, 8.1.1, or 8.2.0 for the latest major version with the fix
- 7. After upgrade, verify that 2FA is enforced and deactivated users cannot log in via DDP Streamer
- 8. Review Rocket.Chat upgrade documentation for any migration steps specific to your version path
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30831 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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