CVE-2026-110631: Komodo through 2.3.3 Periphery Agent Unauthenticated RCE via Default Configuration

Published Oct 14, 2026
·
Updated

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 issue Periphery API requests, including terminal sessions and container operations, executing commands on managed hosts typically as root.

Affected Software

1 affected component
Komodo Periphery Agent<=2.3.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Configure non-empty core_public_keys and passkeys lists so the Periphery agent does not accept unauthenticated connections as a trusted Core.

    Komodo Periphery Agent core_public_keys and passkeys = non-empty

Event History

Oct 14, 2026
CVE Published
via MITRE·02:17 PM
Data Sourced
via MITRE·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Periphery agents reachable on port 8120 are exposed when both the core_public_keys and passkeys lists are empty. This is the default fail-open configuration described for affected Komodo versions through 2.3.3.

2

What does an attacker need to exploit this issue?

An attacker needs network reachability to the Periphery agent on port 8120. No valid credentials, prior access, or user interaction is required; the attacker can present an arbitrary generated keypair as a trusted Core.

3

What access can exploitation provide?

An attacker can issue Periphery API requests, including starting terminal sessions and performing container operations. Commands on managed hosts typically execute as root.

4

What can be done if patching is not immediately possible?

Restrict network access to port 8120 so untrusted systems cannot reach Periphery agents. Configure non-empty core_public_keys and/or passkeys lists rather than leaving both authentication lists empty.

5

How can I determine whether an agent is currently at risk?

Check whether the Periphery agent is reachable on port 8120 and inspect its configuration for empty core_public_keys and passkeys lists. An agent meeting both conditions is vulnerable to unauthenticated connections as a trusted Core.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203