CVE-2026-110631

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-14. A secondary CVSS source baseline 9.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
9.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.7%CVSS: 9.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.

The CVE record's CNA (VulnCheck) lists moghtech komodo versions up to and including 2.3.3 as affected. No release containing a fix is confirmed on record.

Komodo through 2.3.3 contains an authentication bypass vulnerability in the Periphery agent that allows unauthenticated attackers to connect as a trusted Core because empty core_public_keys and passkeys lists fail open by default. Attackers reaching port 8120 can present any generated keypair to issue Periphery API requests, including terminal sessions and container operations, executing commands on managed hosts typically as root.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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.7%
EPSS %ILE
53rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

October 14, 2026

Last Modified

October 20, 2026

Advisory Details (8)

Auto-updated Oct 20, 2026
🔬 Proof of concept available. No fix on record yet.
Web page🟡 PoC Available

CVE-2026-110631: Anyone Could Run Commands on Your Komodo Hosts — Fail-Open Auth in Periphery | Ravindu Lakmina Munaweera - Security Research

https://ravindulakmina.pages.dev/advisories/cve-2026-110631-komodo-periphery-fail-open-rce/
Web page

https://ravindulakmina.pages.dev/advisories/cve-2026-110631-komodo-periphery-fail-open-rce/

https://ravindulakmina.pages.dev/advisories/komodo-periphery-fail-open-rce/
Web page

Insecure default: Periphery authorizes any client when no core_public_keys/passkeys are configured (unauthenticated access to host-management API) · Issue #1690 · moghtech/komodo · GitHub

https://github.com/moghtech/komodo/issues/1690
Web page

komodo/config/periphery.config.toml at v2.3.3 · moghtech/komodo · GitHub

https://github.com/moghtech/komodo/blob/v2.3.3/config/periphery.config.toml
Web page

komodo/bin/periphery/src/state.rs at v2.3.3 · moghtech/komodo · GitHub

https://github.com/moghtech/komodo/blob/v2.3.3/bin/periphery/src/state.rs#L82-L88
Web page

komodo/bin/periphery/src/connection/server.rs at v2.3.3 · moghtech/komodo · GitHub

https://github.com/moghtech/komodo/blob/v2.3.3/bin/periphery/src/connection/server.rs
Web page

komodo/bin/periphery/src/api/router.rs at v1.19.5 · moghtech/komodo · GitHub

https://github.com/moghtech/komodo/blob/v1.19.5/bin/periphery/src/api/router.rs
Web page

Komodo through 2.3.3 Periphery Agent Unauthenticated RCE via Default Configuration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/komodo-through-2.3.3-periphery-agent-unauthenticated-rce-via-default-configuration

Vendor Advisories for CVE-2026-110631(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 23× in last 7d / 30× 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-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-21 15:50 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-20 17:15 UTCEG score recompute
  4. 2026-10-20 17:15 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-20 02:26 UTCEG score recompute
  7. 2026-10-20 02:26 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-20 01:34 UTCEG score recompute
  9. 2026-10-20 01:33 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-19 08:53 UTCEG score recompute
  12. 2026-10-19 08:53 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-18 10:21 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-18 05:06 UTCEG score recompute
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-17 10:21 UTCEG score recompute
  17. 2026-10-17 10:21 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-16 11:49 UTCEG score recompute
  20. 2026-10-16 11:49 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-16 00:18 UTCEG score recompute
  22. 2026-10-16 00:17 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-14 16:32 UTCEG score recompute
  25. 2026-10-14 16:31 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 5 more
  1. 2026-10-14 15:41 UTCEG score recompute
  2. 2026-10-14 15:40 UTCGHSA enrichmentGHSA-6388-9x82-rf3x · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-14 15:28 UTCEG score recompute
  4. 2026-10-14 14:32 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  5. 2026-10-14 14:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-110631?
CVE-2026-110631 is a critical-severity vulnerability; its CVE record was published on October 14, 2026. Komodo through 2.3.3 contains an authentication bypass vulnerability in the Periphery agent that allows unauthenticated attackers to connect as a trusted Core because empty corepublickeys and passkeys lists fail open by default. Attackers reaching port 8120 can present any generated keypair to…
When was CVE-2026-110631 made public?
CVE-2026-110631 was made public on October 13, 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 October 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-110631 actively exploited?
CVE-2026-110631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-110631?
CVE-2026-110631 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-110631?
No fix for CVE-2026-110631 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 CVE record's CNA (VulnCheck) lists moghtech komodo versions up to and including 2.3.3 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-110631 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-110631?

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