Quick answers
- Is CVE-2026-81836 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81836 being exploited in the wild.
- How severe is CVE-2026-81836?
- Low severity, with a CVSS score of 3.7, published 28 August 2026.
- Which products and versions are affected?
- RooCodeInc Roo Code up to 3.51.1.
- Is there a fix for CVE-2026-81836?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81836 attacked?
- It is attacked from the adjacent network or over the network.
- Am I affected by CVE-2026-81836?
- Check whether you run RooCodeInc Roo Code at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a cleartext transmission of sensitive information (CWE-319) in the OAuth callback implementation. The root cause lies in src/integrations/claude-code/oauth.ts where the redirect URI is hardcoded as "http://localhost:54545/callback" instead of using HTTPS. An attacker on the same network can intercept the OAuth authorization code transmitted in cleartext HTTP traffic via ARP spoofing or packet sniffing, then exchange it for an access token to hijack the victim's account. The attack requires the attacker and victim to be on the same network and the victim to initiate OAuth login, but no additional authentication or user interaction beyond that is required. The project is no longer maintained by the vendor, and no patches are available.
Affected products
- RooCodeInc Roo-Code up to 3.51.1
Timeline
- 2026-08-28: disclosed
- exploited: Public proof-of-concept available