VulnerabilityPublished 6 Mar 2026Updated 9 Mar 2026

CVE-2026-30833: RocketChat Rocket.Chat · Improper Neutralization of Special Elements in Data Query Logic

Affects RocketChat Rocket.ChatSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.9 Medium · fixed in 8.2.0 : update RocketChat Rocket.Chat when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.2.0, 8.1.1, 8.0.2 +4

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
RocketChatRocket.Chat	Affected <8.2.0	Fixed in 8.2.0
RocketChatRocket.Chat	Affected <8.1.1	Fixed in 8.1.1
RocketChatRocket.Chat	Affected <8.0.2	Fixed in 8.0.2
RocketChatRocket.Chat	Affected <7.13.4	Fixed in 7.13.4
RocketChatRocket.Chat	Affected <7.12.5	Fixed in 7.12.5
RocketChatRocket.Chat	Affected <7.11.5	Fixed in 7.11.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Rocket.Chat to one of the patched versions: 7.10.8, 7.11.5, 7.12.5, 7.13.4, 8.0.2, 8.1.1, or 8.2.0. If upgrading is not immediately feasible, implement strict input validation and sanitization on the username fields at the application or proxy level to block injection patterns such as MongoDB operators. Employ Web Application Firewalls (WAFs) with custom rules to detect and block NoSQL injection payloads targeting the login endpoint. Monitor authentication logs for anomalous login attempts or patterns indicative of injection attacks. Conduct a thorough review of user account access and audit for suspicious activity. Limit exposure by restricting access to the Rocket.Chat service to trusted networks or VPNs where possible. Educate development teams on secure coding practices to prevent injection flaws, emphasizing the importance of parameterized queries or query builders that separate data from code. Finally, maintain up-to-date backups and incident response plans to quickly recover in case of compromise.

Description

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.

Impact

The primary impact of this vulnerability is unauthorized access to Rocket.Chat accounts without valid credentials, undermining the confidentiality and integrity of communications. Attackers exploiting this flaw can impersonate legitimate users, potentially gaining access to sensitive conversations, private channels, and organizational data. This can lead to data leakage, espionage, or further lateral movement within an organization’s network. Since Rocket.Chat is often deployed in enterprise, government, and educational environments for secure collaboration, exploitation could disrupt trust and operational security. Additionally, unauthorized access could enable attackers to escalate privileges or deploy further attacks such as social engineering or malware distribution. The vulnerability affects all organizations using vulnerable Rocket.Chat versions, with a higher risk for those with sensitive or regulated data. The lack of required authentication and user interaction increases the likelihood of automated exploitation attempts if weaponized. However, no known exploits in the wild currently reduce immediate widespread impact but do not eliminate future risk.

CWE-943Improper Neutralization of Special Elements in Data Query Logic (opens in a new tab)
Class weakness
The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
NoSQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-hgq6-9jg2-wf3f (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Mar 2026, 19:47 UTC

WeaknessesCWE-943

Technical details

References

Community reviews

Related threats