RooCodeInc Roo-Code up to 3.51.1 OAuth Callback oauth.ts cleartext transmission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 2.72 |
Summary
A vulnerability marked as problematic has been reported in RooCodeInc Roo-Code up to 3.51.1. This issue affects some unknown processing of the file src/integrations/claude-code/oauth.ts of the component OAuth Callback. This manipulation causes cleartext transmission. This vulnerability only affects products that are no longer supported by the maintainer. The identification of this vulnerability is CVE-2026-81836. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it."
Details
A vulnerability was found in RooCodeInc Roo-Code up to 3.51.1. It has been declared as problematic. Affected by this vulnerability is an unknown code of the file src/integrations/claude-code/oauth.ts of the component OAuth Callback. The manipulation with an unknown input leads to a cleartext transmission vulnerability. The CWE definition for the vulnerability is CWE-319. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. As an impact it is known to affect confidentiality.
The advisory is shared at gist.github.com. This vulnerability is known as CVE-2026-81836. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1040 for this issue.
It is possible to download the exploit at gist.github.com. It is declared as proof-of-concept. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it."
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Support
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.7
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cleartext transmissionCWE: CWE-319 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/27/2026 Advisory disclosed08/27/2026 VulDB entry created
08/27/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-81836 (🔒)
GCVE (CVE): GCVE-0-2026-81836
GCVE (VulDB): GCVE-100-396169
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/27/2026 16:54Changes: 08/27/2026 16:54 (57)
Complete: 🔍
Submitter: tchen200311
Cache ID: 216::103
Submit
Accepted
- Submit #864287: Roo-Code v3.51.1 Cleartext Transmission of Sensitive Information (by tchen200311)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.