CVE-2026-81836RooCodeInc Roo-Code OAuth Callback oauth.ts cleartext transmission
Updated under an hour ago ()
Does this affect you?
It affects RooCodeInc Roo-Code. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
A vulnerability was detected in RooCodeInc Roo-Code up to 3.51.1. This vulnerability affects unknown code of the file src/integrations/claude-code/oauth.ts of the component OAuth Callback. The manipulation results in cleartext transmission of sensitive information. The attack may be performed from remote. A high complexity level is associated with this attack. It is stated that the exploitability is difficult. The exploit is now public and may be used. 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." This vulnerability only affects products that are no longer supported by the maintainer.
- CVSS
- 3.7 LOW (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
- Weakness (CWE)
- CWE-319, CWE-310
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulDB
- NVD analysis
- Deferred
- Record last updated
- Aug 31, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
RooCodeInc Roo-Code roocodeinc:roo-code | 3.51.0; 3.51.1 | CNA record |
References
- https://vuldb.com/vuln/396169vdb-entry
- https://vuldb.com/vuln/396169/ctisignature, permissions-required
- https://vuldb.com/cve/CVE-2026-81836third-party-advisory
- https://vuldb.com/submit/864287third-party-advisory
- https://gist.github.com/tchen200311/dcf3d36781e8246876cde7965fdda490exploit
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.