CVE-2026-17113

Cri-o: cri-o: unvalidated image env var causes daemon crash

State
Published
Severity
6.0 Medium
Published
Aug 24, 2026
Updated
Oct 21, 2026
Reserved
Jul 24, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.16.0 MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:Hredhat

Weaknesses

  • CWE-1287 Improper Validation of Specified Type of Input

Affected Products

ProductVersions
cri-o
  • before 1.34.11Affected
  • before 1.35.7Affected
  • before 1.36.3Affected
Red Hat OpenShift Container Platform 4Red Hat
    Red Hat OpenShift Container Platform 4Red Hat
      Red Hat OpenShift Container Platform 4Red Hat
        Red Hat OpenShift Container Platform 4Red Hat

          References

          Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.