A flaw was found in CRI-O's container-creation environment-variable handling (`mergeEnvs` in `server/utils.go`…
Summary
Vulnerability reported (CVE-2026-17113). Risk of unauthorized operations or information disclosure. Exploitable via mergeEnvs.
Original description
The description as published by the source.
A flaw was found in CRI-O's container-creation environment-variable handling
(mergeEnvs in server/utils.go, consumed by setupContainerEnvironmentAndWorkdir in
server/container_create.go). When a CreateContainer request supplies a nil CRI
Envs field, CRI-O falls back to using the target OCI image's config.Env entries
unfiltered, in contrast to the normal merge path, which validates each entry for a
key=value form before use. An OCI image whose config.Env contains an entry with no
= character (e.g. a bare NOEQUALS string) causes CRI-O to split that entry into a
single-element slice and then index its second element, which is out of range. This
triggers an unrecovered Go runtime panic in the crio daemon process, crashing it and
terminating the container-runtime service for all workloads on the node until it is
restarted.
Source: NIST National Vulnerability Database NVD
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-17113 has been found.
Attackers can target a specific entry point like mergeEnvs over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-17113" on the vendor's site.
CVE-2026-17113 — CWE-1287 / CVSS v3 6.0
Attack vector: local / no user interaction
Attack surface: mergeEnvs / setupContainerEnvironmentAndWorkdir / CreateContainer / nil
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 (CWE-1287) has been reported. Attackers reach the vulnerable code path via mergeEnvs.
Check the vendor advisory for the affected versions. Attack surface: mergeEnvs / setupContainerEnvironmentAndWorkdir / CreateContainer / nil.
Severity: Medium (CVSS 6.0/10). 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 でアラート再発が無いか継続監視。