CVE-2026-17113

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 24, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
No fix on record yet. Sources: redhat.
redhat

2506872 – (CVE-2026-17113) CVE-2026-17113 cri-o: CRI-O: unvalidated image env var causes daemon crash

https://bugzilla.redhat.com/show_bug.cgi?id=2506872
redhatMentions a patch (unverified)

CVE-2026-17113 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-17113

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-10 19:59 UTCEPSS rescore
  2. 2026-10-10 12:29 UTCEG score recompute
  3. 2026-10-09 20:06 UTCEPSS rescore
  4. 2026-10-09 04:41 UTCEG score recompute
  5. 2026-10-08 17:11 UTCEPSS rescore
  6. 2026-10-08 03:48 UTCEG score recompute
  7. 2026-10-07 23:47 UTCEPSS rescore
  8. 2026-10-07 01:11 UTCEG score recompute
  9. 2026-10-06 15:17 UTCEPSS rescore
  10. 2026-10-06 02:45 UTCEG score recompute
  11. 2026-10-05 17:42 UTCEPSS rescore
  12. 2026-10-05 01:26 UTCEG score recompute
  13. 2026-10-04 23:21 UTCEPSS rescore
  14. 2026-10-02 03:40 UTCEG score recompute
  15. 2026-10-01 19:49 UTCEPSS rescore
  16. 2026-10-01 05:37 UTCEG score recompute
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 06:58 UTCEG score recompute
  19. 2026-09-29 15:20 UTCEPSS rescore
  20. 2026-09-28 21:32 UTCEG score recompute
  21. 2026-09-26 22:16 UTCEG score recompute
  22. 2026-09-26 15:58 UTCEPSS rescore
  23. 2026-09-24 18:53 UTCEG score recompute
  24. 2026-09-23 19:58 UTCEG score recompute
  25. 2026-09-22 21:47 UTCEG score recompute
Show 42 more
  1. 2026-09-21 23:45 UTCEG score recompute
  2. 2026-09-21 01:42 UTCEG score recompute
  3. 2026-09-20 03:10 UTCEG score recompute
  4. 2026-09-18 07:06 UTCEG score recompute
  5. 2026-09-17 09:04 UTCEG score recompute
  6. 2026-09-16 14:07 UTCEPSS rescore
  7. 2026-09-15 12:58 UTCEG score recompute
  8. 2026-09-13 16:54 UTCEG score recompute
  9. 2026-09-13 16:46 UTCEPSS rescore
  10. 2026-09-11 20:50 UTCEG score recompute
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-11 09:36 UTCEPSS rescore
  13. 2026-09-10 22:33 UTCEG score recompute
  14. 2026-09-10 09:34 UTCEPSS rescore
  15. 2026-09-09 01:21 UTCEG score recompute
  16. 2026-09-08 22:00 UTCEPSS rescore
  17. 2026-09-07 04:49 UTCEG score recompute
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-06 06:46 UTCEG score recompute
  20. 2026-09-05 08:44 UTCEG score recompute
  21. 2026-09-04 10:41 UTCEG score recompute
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-01 16:19 UTCEG score recompute
  24. 2026-09-01 13:53 UTCEPSS rescore
  25. 2026-09-01 04:39 UTCEPSS rescore
  26. 2026-08-31 17:41 UTCEG score recompute
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 17:31 UTCEG score recompute
  29. 2026-08-30 01:22 UTCEPSS rescore
  30. 2026-08-29 19:28 UTCEG score recompute
  31. 2026-08-28 21:41 UTCEPSS rescore
  32. 2026-08-27 17:21 UTCEG score recompute
  33. 2026-08-27 17:14 UTCEG score recompute
  34. 2026-08-27 14:25 UTCEPSS rescore
  35. 2026-08-27 11:29 UTCEG score recompute
  36. 2026-08-26 14:46 UTCEPSS rescore
  37. 2026-08-25 15:22 UTCEG score recompute
  38. 2026-08-25 15:16 UTCEG score recompute
  39. 2026-08-25 13:48 UTCEPSS rescore
  40. 2026-08-24 22:26 UTCEG score recompute
  41. 2026-08-24 21:33 UTCEG score recompute
  42. 2026-08-24 21:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17113?
CVE-2026-17113 is a medium vulnerability published on August 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…
When was CVE-2026-17113 disclosed?
CVE-2026-17113 was first published on August 24, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17113 actively exploited?
CVE-2026-17113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17113?
CVE-2026-17113 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17113?
No fix for CVE-2026-17113 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17113

Explore →

Is Your Infrastructure Affected by CVE-2026-17113?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs