CVE-2026-101062

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-27. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-88033 (ENISA EUVD) · GHSA-cfp9-746c-5jrw (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Obot before v0.23.0 (affected versions <= v0.22.1) running with OBOT_SERVER_ENABLE_AUTHENTICATION=true exposes OAuth dynamic client registration without authentication and without any restriction on the redirect URIs a client may register. Because the authorization flow auto-completes for an already logged-in user with no consent screen, an attacker who registers a client pointing at their own domain and induces a logged-in victim to visit a single crafted authorization URL receives an authorization code at the attacker-controlled redirect URI and can exchange it for an access token and refresh token. The token minted by the MCP OAuth flow carries the victim's full group set in the JWT, and Obot validated only the issuer and not the audience, so the token is accepted as a bearer token against any Obot API endpoint the victim can access rather than being scoped to the requested MCP server, allowing the attacker to read or modify the victim's resources until the token is revoked. v0.23.0 adds a consent screen, restricts MCP OAuth tokens to the MCP involved in the request, and enforces audience validation.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 27, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 27, 2026
Patch available. Sources: github.
Web page

Obot before v0.23.0 Authentication Bypass via OAuth Dynamic Client Registration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/obot-before-0.23.0-authentication-bypass-via-oauth-dynamic-client-registration
GitHub advisoryMentions a patch (unverified)

OAuth Dynamic Client Registration Enables API Token Theft via Audience Confusion · Advisory · obot-platform/obot · GitHub

https://github.com/obot-platform/obot/security/advisories/GHSA-xwmw-prc4-v3cr

Vendor Advisories for CVE-2026-101062(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/obot-platform/obot—
  • every version up to 0.23.0: fixed in 0.23.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-27 21:32 UTCEG score recompute
  7. 2026-10-27 21:32 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-10-25 15:57 UTCEG score recompute
  12. 2026-10-24 20:55 UTCEG score recompute
  13. 2026-10-24 20:55 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-18 05:11 UTCEG score recompute
  22. 2026-10-17 20:00 UTCEG score recompute
  23. 2026-10-17 20:00 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 68 more
  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-12 16:41 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-11 20:16 UTCEG score recompute
  7. 2026-10-11 18:19 UTCEG score recompute
  8. 2026-10-11 18:19 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-11 15:02 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-11 06:01 UTCEG score recompute
  12. 2026-10-11 06:01 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-10 17:53 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-10-10 05:47 UTCEG score recompute
  16. 2026-10-10 05:47 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-10-09 17:39 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-09 04:59 UTCEG score recompute
  20. 2026-10-09 04:59 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-10-08 16:52 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-08 01:42 UTCEG score recompute
  24. 2026-10-08 01:42 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-10-07 13:35 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  27. 2026-10-07 01:19 UTCEG score recompute
  28. 2026-10-07 01:19 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  29. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  30. 2026-10-06 13:12 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  31. 2026-10-06 01:05 UTCEG score recompute
  32. 2026-10-06 01:05 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-10-05 12:58 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-10-05 00:51 UTCEG score recompute
  36. 2026-10-05 00:50 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  37. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-10-04 12:40 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-10-04 00:32 UTCEG score recompute
  40. 2026-10-04 00:32 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  41. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  42. 2026-10-03 12:26 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  43. 2026-10-03 00:19 UTCEG score recompute
  44. 2026-10-03 00:19 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-10-02 12:12 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-10-02 00:02 UTCEG score recompute
  47. 2026-10-02 00:02 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-10-01 11:39 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  50. 2026-09-30 23:31 UTCEG score recompute
  51. 2026-09-30 23:31 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-09-30 22:26 UTCEG score recompute
  53. 2026-09-30 22:26 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-09-30 11:53 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-09-29 23:46 UTCEG score recompute
  57. 2026-09-29 23:46 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-09-29 09:19 UTCEG score recompute
  60. 2026-09-29 09:19 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-09-28 21:13 UTCEG score recompute
  62. 2026-09-28 21:13 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  64. 2026-09-28 09:32 UTCEG score recompute
  65. 2026-09-28 09:32 UTCGHSA enrichmentGHSA-cfp9-746c-5jrw · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-09-27 21:26 UTCEG score recompute
  67. 2026-09-27 21:00 UTCEG score recomputeFirst assessed: 8.8 HIGH
  68. 2026-09-27 21:00 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-101062?
CVE-2026-101062 is a high-severity vulnerability; its CVE record was published on September 27, 2026. Obot before v0.23.0 (affected versions <= v0.22.1) running with OBOT_SERVER_ENABLE_AUTHENTICATION=true exposes OAuth dynamic client registration without authentication and without any restriction on the redirect URIs a client may register. Because the authorization flow auto-completes for an…
When was CVE-2026-101062 made public?
CVE-2026-101062 was made public on June 22, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-101062 actively exploited?
CVE-2026-101062 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101062?
CVE-2026-101062 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101062?
A fix for CVE-2026-101062 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101062 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-101062

Explore →

Is Your Infrastructure Affected by CVE-2026-101062?

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

Book a Demo →Browse All CVEs