Skip to main content

Komodo Periphery EUVDEUVD-2026-101259

| CVE-2026-110631 CRITICAL
Initialization of a Resource with an Insecure Default (CWE-1188)
2026-10-14 VulnCheck GHSA-6388-9x82-rf3x
9.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Periphery agent on port 8120
  2. Delivery
    Generate arbitrary keypair
  3. Exploit
    Present as trusted Core (fail-open)
  4. Execution
    Issue Periphery API terminal/container request
  5. Impact
    Execute commands as root on managed host

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V13 - Configuration Secure default settings
Exploitation Conditions

No special conditions in the default deployment: the Periphery agent ships with empty core_public_keys and passkeys lists, which fail open and accept any attacker-supplied keypair as a trusted Core - so an unconfigured, network-reachable agent is exploitable out of the box. The concrete prerequisite is network reachability to the Periphery agent's TCP port 8120. The primary LIMITING factor is that Periphery is designed to be reached only by the Core; instances where 8120 is firewalled or bound to a trusted management network/localhost are not remotely exploitable, and explicitly populating core_public_keys or passkeys closes the bypass. There is no user interaction and no authentication requirement (PR:N confirmed).

Impact

This is a genuine high-priority issue, not a CVSS-inflated paper risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VC:H/VI:H/VA:H, score 9.3) is fully consistent with the description: a network-reachable Periphery agent on port 8120 that fails open when core_public_keys and passkeys are empty - the default state - allowing an unauthenticated attacker to present any self-generated keypair and gain full API control, including terminal sessions and container operations that execute commands (typically as root) on managed hosts. CWE-1188 (insecure default initialization) matches precisely: the danger is in the shipped default, so any exposed-but-unconfigured instance is exploitable with no further conditions. Signals that are MISSING: no EPSS score was provided, this CVE is NOT in CISA KEV, and no POC flag was supplied, so there is no evidence of active exploitation or weaponization at this time - the urgency derives from exploit simplicity and impact, not from observed in-the-wild activity. The main mitigating factor is exposure scope: Periphery agents are intended to be reached only by the trusted Core, so risk concentrates on instances where port 8120 is reachable from untrusted networks (internet-exposed or flat internal networks).

Exploit ScenarioDerived

An attacker scans for or discovers a Komodo Periphery agent listening on TCP port 8120 that was deployed with the default empty core_public_keys/passkeys configuration. Because authentication fails open, the attacker generates an arbitrary keypair, connects as a 'trusted' Core, and issues Periphery API calls to open a terminal session or manipulate containers - executing arbitrary commands on the managed host, typically with root privileges. No public exploit was identified at time of analysis, but the attack requires no special tooling and no authentication.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Unauthenticated remote code execution affects Komodo through 2.3.3 via its Periphery agent, which fails open when its core_public_keys and passkeys allowlists are left empty - the shipping default. Any attacker who can reach the agent's TCP port 8120 can present a self-generated keypair, be accepted as a trusted Core, and issue Periphery API calls that include terminal sessions and container operations, resulting in command execution on managed hosts typically as root. The CVSS 4.0 base score is 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N, high confidentiality/integrity/availability), consistent with an independent assessment of CVSS 3.1 9.3; no public exploit code and no CISA KEV entry were identified at time of analysis, though the default-configuration exposure makes exploitation trivial wherever port 8120 is reachable.

RemediationAI

No vendor-released patch version is identified in the available data; remediation status should be tracked through the upstream issue at https://github.com/moghtech/komodo/issues/1690 and the advisory at https://www.vulncheck.com/advisories/komodo-through-2.3.3-periphery-agent-unauthenticated-rce-via-default-configuration, and operators should upgrade to the first release later than 2.3.3 that the maintainer marks as fixed rather than assuming 2.3.3 is safe. The most direct compensating control is to explicitly populate core_public_keys (and passkeys, if used) in periphery.config.toml with the exact public key(s) of the legitimate Core, which closes the fail-open behavior; the trade-off is that any Core or client not holding a listed key will be rejected until its key is added, so generate and distribute keys before rolling this out. Where key configuration cannot be completed immediately, restrict network reachability to the Periphery listener: firewall TCP port 8120 so only the Core's address can connect, or bind Periphery to localhost/a dedicated management interface; the trade-off is that this breaks Core-to-Periphery connectivity if the Core is not on the same trusted segment, and any pre-existing over-permissive network rules must be audited. Given the agent's effective root-level command and container control, treat any deployment that had 8120 exposed with default configuration as potentially compromised and rotate credentials and audit host activity.

Affected VersionsENISA

komodo 0 ≤2.3.3

Affected Packages

euvd komodo no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Komodo is a self-hosted infrastructure/container management platform split into a Core controller and Periphery agents (written in Rust) deployed on managed hosts. The Periphery agent authenticates an inbound Core by verifying the keypair it presents against the core_public_keys and, optionally, passkeys lists defined in periphery.config.toml (see bin/periphery/src/state.rs and bin/periphery/src/connection/server.rs at tag v2.3.3). Because those lists are empty by default, the verification logic treats 'no configured trusted keys' as 'trust anything' rather than 'trust nothing' - the classic insecure default initialization pattern mapped to CWE-1188. The result is a total authentication bypass on the Periphery listener (TCP 8120): a remote, unauthenticated party is indistinguishable from a legitimate Core and gains the full Periphery API surface, including interactive terminal access and container/host operations. The CPE cpe:2.3:a:moghtech:komodo:*:*:*:*:*:*:*:* is version-agnostic, and the advisory scopes the flaw to Komodo through 2.3.3; historical code at v1.19.5 (bin/periphery/src/api/router.rs) is referenced, suggesting the insecure default has existed across a long release history rather than being newly introduced.

Know when Komodo gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 9.3 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 9.8 CRITICAL

Remote, network-reachable agent with fail-open default means no privileges and low complexity (PR:N/AC:L), yielding full host command execution and thus C/I/A High.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Organizations running Komodo at version 2.3.3 or earlier are exposed to unauthenticated remote code execution through the bundled Periphery agent, which ships in a fail-open configuration that accepts any self-generated keypair as trusted. An attacker who can reach TCP port 8120 gains root-level command execution and container control across every managed host, turning a single reachable port into full compromise of the managed fleet. Leadership should care because the exposure exists in the shipping default - no misconfiguration by internal teams is required - and the affected hosts typically hold production workloads, credentials, and lateral movement paths.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: block or restrict inbound TCP port 8120 to a trusted management network; populate the Periphery agent's core_public_keys and passkeys allowlists so the fail-open default no longer applies; network-segment managed hosts away from general corporate and internet-facing ranges; terminate agent traffic through an authenticated proxy or jump host; enable Periphery API and terminal session logging with alerting on unrecognized keypair acceptance and unexpected container operations.

Threat Intelligence Overview

EPSS Score
0.7%
Top 47% exploitable
Prevalence
Low
self-hosted container orchestration tool, mostly homelab/small-team, limited enterprise footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy