CVE-2026-88862

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-10. 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 weekElevated
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

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

Capgo (capgo.app) backend through 12.242.4 does not validate parent-child delegation when processing the x-limited-key-id header. checkKeyByIdPg() in supabase/functions/_backend/utils/hono_middleware.ts resolves the attacker-supplied numeric API key ID using only the key ID, its expiration state, and the authenticating key's user_id, while hasLimitedRbacSubkeyScope() accepts any key with a non-organization (e.g., app-scoped) RBAC binding and validateSubkeyUser() only compares owning user IDs. Because Capgo treats API keys as independent RBAC principals with separate role bindings, an authenticated apikey_manager API key with no application access can supply the numeric ID of a more privileged same-owner key and have the middleware replace the authenticated principal and effective API-key secret with that key (setSubkeyAuthContext), exercising an app_admin sibling's permissions without knowing or submitting its secret. The issue was reproduced on release 12.242.4 (commit b3d02cdbc23ac59990785acacd1f113c07458568) after the fix for GHSA-8h52-44r7-w343; at the time of the advisory no patched version was available.

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

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (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.

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 10, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 10, 2026
No fix on record yet. Sources: github.
Web page

Capgo API Key Manager Authentication Bypass via x-limited-key-id | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-api-key-manager-authentication-bypass-via-x-limited-key-id
GitHub advisoryMentions a patch (unverified)

API key manager can impersonate a protected same-owner app-admin key via x-limited-key-id · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo.app/security/advisories/GHSA-5hjr-xhx8-x5j7

Vendor Advisories for CVE-2026-88862(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 118× 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.

Showing the most recent 100 of 129 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88862?
CVE-2026-88862 is a high-severity vulnerability; its CVE record was published on September 10, 2026. Capgo (capgo.app) backend through 12.242.4 does not validate parent-child delegation when processing the x-limited-key-id header. checkKeyByIdPg() in supabase/functions/backend/utils/honomiddleware.ts resolves the attacker-supplied numeric API key ID using only the key ID, its expiration state, and…
When was CVE-2026-88862 made public?
CVE-2026-88862 was made public on August 27, 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 10, 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-88862 actively exploited?
CVE-2026-88862 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88862?
CVE-2026-88862 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-88862?
No fix for CVE-2026-88862 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-88862 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-88862?

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

Book a Demo →Browse All CVEs