VulnerabilityPublished 14 Jan 2026

CVE-2026-23477: RocketChat Rocket.Chat · Improper Privilege Management

Affects RocketChat Rocket.ChatSource CVE Database V5

Not known to be exploited · CVSS 7.7 High : upgrade to 6.12.0 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.7High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.12.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 Rocket.Chat and rocketchat/Rocket.Chat to 6.12.0.

Affected software

Product	Affected	Fixed in
RocketChatRocket.Chat	Affected <6.12.0	Fixed in 6.12.0
GitHubrocketchat/Rocket.Chat`pkg:github/rocketchat/Rocket.Chat`Other threats	Affected <6.12.0	Fixed in 6.12.0

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

AI-suggested

Upgrade all Rocket.Chat instances to version 6.12.0 or later immediately to apply the official fix that enforces proper authorization on the OAuth apps API endpoint.
Audit existing OAuth applications and rotate client secrets to invalidate any potentially compromised credentials.
Implement strict access controls and monitoring on Rocket.Chat authentication to detect anomalous access patterns, especially from low-privilege accounts.
Limit the number of users with authenticated access to Rocket.Chat and enforce strong authentication mechanisms such as MFA.
Review and restrict API access logs to identify any unauthorized queries to the /api/v1/oauth-apps.get endpoint.
Educate users about the risks of credential exposure and encourage reporting of suspicious activity.
Consider network segmentation to isolate Rocket.Chat servers and reduce exposure to internal threats.
Employ runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block unauthorized API calls if upgrading is temporarily not feasible.

Description

CVE-2026-23477 is a high-severity privilege management vulnerability in Rocket. Chat versions prior to 6.12.0. It allows any authenticated user, regardless of role or permissions, to access the GET /api/v1/oauth-apps.get API endpoint. This endpoint exposes OAuth application details, including sensitive client_id and client_secret fields, if the user knows the OAuth app ID. The vulnerability does not require user interaction and can be exploited remotely with low complexity. While no exploits are currently known in the wild, the exposure of OAuth credentials can lead to unauthorized access to integrated services. The issue is fixed in Rocket.

Impact

For European organizations, the impact of this vulnerability can be substantial. Rocket.Chat is commonly used in enterprises, government agencies, and critical infrastructure sectors for secure communications. Exposure of OAuth client credentials can lead to unauthorized access to connected services, data leakage, and potential lateral movement within networks. This could compromise confidentiality of sensitive communications and integrated applications. Since the vulnerability requires only authenticated access, any compromised or malicious internal user can exploit it, increasing insider threat risks. The lack of integrity or availability impact reduces the chance of direct service disruption, but the confidentiality breach alone can have severe regulatory and reputational consequences under GDPR and other data protection laws. Organizations in sectors with stringent compliance requirements, such as finance, healthcare, and public administration, are particularly vulnerable. The potential for scope change means attackers could leverage stolen credentials to access other systems, amplifying the overall risk.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-g4wm-fg3c-g4p2 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 20:38 UTC

WeaknessesCWE-269, CWE-862

Technical details

References

Community reviews

Related threats