Answer in brief
CVE-2026-17113 records a Medium severity (CVSS 6.0) vulnerability in Cri-o: cri-o: unvalidated image env var causes daemon crash. The current sources do not mark it as known exploited. The current feed maps cri-o (generic), Red Hat/cri-o (generic), Red Hat/openshift/ose-rhel-coreos-8 (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps cri-o (generic), Red Hat/cri-o (generic), Red Hat/openshift/ose-rhel-coreos-8 (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| cri-ogeneric | >=0 <1.34.11 || >=0 <1.35.7 || >=0 <1.36.3 | 1.34.11, 1.35.7, 1.36.3 |
| Red Hat/cri-ogeneric | * | Not reported |
| Red Hat/openshift/ose-rhel-coreos-8generic | * | Not reported |
| Red Hat/openshift/ose-rhel-coreos-9generic | * | Not reported |
| Red Hat/rhcosgeneric | * | Not reported |
Published upstream
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.