The `periphery` agent's container-management functionality of Komodo version 2.2.0 contains an OS...
Summary
Vulnerability reported (CVE-2026-110005). Risk of unauthorized operations or information disclosure. Exploitable via periphery.
Original description
The description as published by the source.
The periphery agent's container-management functionality of Komodo version 2.2.0 contains an OS command injection vulnerability. An authenticated low-privileged user with Execute, or Read plus Logs, permission on a managed server can supply shell metacharacters in a container name processed by the DestroyContainer or SearchContainerLog operations. The container name is interpolated without escaping into a command executed using sh -c, allowing arbitrary commands to execute as root on the managed host. This permits a user without Komodo's Terminal permission to obtain unrestricted host-level command execution.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-110005 has been found.
Attackers can target a specific entry point like periphery over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-110005" on the vendor's site.
CVE-2026-110005
Attack surface: periphery / Execute / Read / Logs
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) has been reported. Attackers reach the vulnerable code path via periphery.
Check the vendor advisory for the affected versions. Attack surface: periphery / Execute / Read / Logs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web kb.cert.org
- web nvd.nist.gov
- web github.com