# CVE-2026-23477: Rocket.Chat Unauthorized Access to OAuth App Details

> Authenticated users can access sensitive OAuth client secrets via an unprotected API endpoint, potentially leading to credential theft.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2026
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-g4wm-fg3c-g4p2

## What is CVE-2026-23477?

CVE-2026-23477 is a high-severity missing authorization vulnerability in Rocket.chat Rocket.chat, published on 14 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rocket.Chat is an open-source, secure, fully customizable communications platform. In Rocket.Chat versions up to 6.12.0, the API endpoint GET /api/v1/oauth-apps.get is exposed to any authenticated user, regardless of their role or permissions. This endpoint returns an OAuth application, as long as the user knows its ID, including potentially sensitive fields such as client_id and client_secret. This vulnerability is fixed in 6.12.0.

Weakness: CWE-862 (Missing Authorization), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-23477?

It affects 1 product.


Products: Rocket.chat Rocket.chat.

## How do I fix CVE-2026-23477?

No fix has been published for CVE-2026-23477 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-23477 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23477 exists.

## Other vulnerabilities in Rocket.chat Rocket.chat

- [CVE-2026-58066](https://insights.sbomify.com/CVE-2026-58066/): Auth bypass in Rocket.Chat (critical 9.8)
- [CVE-2026-29198](https://insights.sbomify.com/CVE-2026-29198/): SQL injection in Rocket.Chat (critical 9.8)
- [CVE-2023-28316](https://insights.sbomify.com/CVE-2023-28316/): Security feature bypass in Rocket.Chat (critical 9.8)
- [CVE-2022-44567](https://insights.sbomify.com/CVE-2022-44567/): Command injection in Rocket.chat - Electron Desktop (critical 9.8)
- [CVE-2021-22910](https://insights.sbomify.com/CVE-2021-22910/): Code injection in Rocket.Chat server (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23477 and fix it if it is affected.

What it is: CVE-2026-23477 is a high-severity missing authorization vulnerability in Rocket.chat Rocket.chat, published on 14 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23477 exists.

Affected product: Rocket.chat Rocket.chat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23477/ (Markdown: https://insights.sbomify.com/CVE-2026-23477/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23477
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23477
- OSV: https://osv.dev/vulnerability/CVE-2026-23477

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23477/
Summaries are generated and may contain mistakes; the official description above is the record.