CVE-2026-81836

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-08-28. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
3.7
EG Score
3.7(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 31, 2026

References (5)

Vendor Advisories for CVE-2026-81836(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 23:46 UTCEG score recompute
  3. 2026-09-16 23:46 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-13 18:08 UTCEG score recompute
  9. 2026-09-13 18:08 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-10 12:30 UTCEG score recompute
  13. 2026-09-10 12:30 UTCGHSA enrichment
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-07 06:51 UTCEG score recompute
  16. 2026-09-07 06:51 UTCGHSA enrichment
  17. 2026-09-06 13:48 UTCEPSS rescore
  18. 2026-09-05 15:31 UTCEPSS rescore
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-04 01:10 UTCEG score recompute
  21. 2026-09-04 01:10 UTCGHSA enrichment
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
Show 16 more
  1. 2026-08-31 19:32 UTCEG score recompute
  2. 2026-08-31 19:32 UTCGHSA enrichment
  3. 2026-08-31 19:20 UTCNVD updateCVSS v4 → 2.9
  4. 2026-08-31 18:34 UTCEG score recompute
  5. 2026-08-31 18:34 UTCGHSA enrichment
  6. 2026-08-31 18:29 UTCMITRE cvelistV5CVSS v4 → 6.3
  7. 2026-08-30 19:18 UTCEPSS rescore
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:42 UTCEPSS rescore
  11. 2026-08-28 15:18 UTCEG score recompute
  12. 2026-08-28 15:18 UTCGHSA enrichment
  13. 2026-08-28 00:31 UTCEG score recompute
  14. 2026-08-28 00:26 UTCNVD updateCVSS v4 → 2.9
  15. 2026-08-27 23:23 UTCEG score recompute
  16. 2026-08-27 23:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81836?
CVE-2026-81836 is a low vulnerability published on August 27, 2026. 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…
When was CVE-2026-81836 disclosed?
CVE-2026-81836 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81836 actively exploited?
CVE-2026-81836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.3% of all scored CVEs.
What is the CVSS score of CVE-2026-81836?
CVE-2026-81836 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-81836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81836, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81836

Explore →

Is Your Infrastructure Affected by CVE-2026-81836?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs