{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-17113 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-17113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-17113 is a medium-severity denial of service vulnerability in Red Hat OpenShift Container Platform 4, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-17113 and fix it if it is affected.\n\nWhat it is: CVE-2026-17113 is a medium-severity denial of service vulnerability in Red Hat OpenShift Container Platform 4, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-17113 in the wild and no public exploit code.\n\nAffected product: Red Hat OpenShift Container Platform 4. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-17113/ (Markdown: https://insights.sbomify.com/CVE-2026-17113/index.md)","id":"CVE-2026-17113","markdown":"https://insights.sbomify.com/CVE-2026-17113/index.md","name":"CVE-2026-17113","record":{"aliases":["AZL-97649"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CRI-O container runtime","requires_auth":"high_privilege","summary":"A malicious OCI image with malformed environment variables can crash the CRI-O daemon, causing a denial of service for all workloads on the node.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1287","name":"Improper Validation of Specified Type of Input"}],"description":"A flaw was found in CRI-O's container-creation environment-variable handling\n(`mergeEnvs` in `server/utils.go`, consumed by `setupContainerEnvironmentAndWorkdir` in\n`server/container_create.go`). When a `CreateContainer` request supplies a `nil` CRI\n`Envs` field, CRI-O falls back to using the target OCI image's `config.Env` entries\nunfiltered, in contrast to the normal merge path, which validates each entry for a\n`key=value` form before use. An OCI image whose `config.Env` contains an entry with no\n`=` character (e.g. a bare `NOEQUALS` string) causes CRI-O to split that entry into a\nsingle-element slice and then index its second element, which is out of range. This\ntriggers an unrecovered Go runtime panic in the `crio` daemon process, crashing it and\nterminating the container-runtime service for all workloads on the node until it is\nrestarted.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cri-o: cri-o: unvalidated image env var causes daemon crash","id":"CVE-2026-17113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Vulnerabilities in IBM AIX and PowerVM VIOS","id":"CVE-2026-17118"},"packages":[],"prev":{"headline":"IBM i is Affected By Multiple Vulnerabilities in SQL","id":"CVE-2026-17111"},"products":["Red Hat OpenShift Container Platform 4"],"published":"2026-08-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Red Hat"]},"summary":"A malicious OCI image with malformed environment variables can crash the CRI-O daemon, causing a denial of service for all workloads on the node.","url":"https://insights.sbomify.com/CVE-2026-17113/"}