A flaw was found in CRI-O. The fix for a previous vulnerability (CVE-2022-4318) was incorrect, allowing it to be bypassed. An attacker capable of setting environment variables on a container can inject a newline character into the HOME environment variable. This issue allows the addition of arbitrary lines into /etc/passwd by use of a specially crafted environment variable.
CVE-2026-15809
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. the CNA's CVSS baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 2.7%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 17, 2026
Advisory Details (5)
Auto-updated Jul 15, 2026[release-1.25] server: fail if HOME variable has a newline
Fix merged in cri-o/cri-o PR #6524 on 2023-02-22 — awaiting tagged release
https://github.com/cri-o/cri-o/pull/6524server: fail if HOME variable has a newline
Patch available: cri-o/cri-o v1.32.10 (PR #6450 merged 2022-12-20)
https://github.com/cri-o/cri-o/pull/64502500846 – (CVE-2026-15809) CVE-2026-15809 github.com/cri-o/cri-o: Fix Bypass for CVE-2022-4318 — /etc/passwd Injection via HOME env
https://bugzilla.redhat.com/show_bug.cgi?id=2500846Vendor Advisories for CVE-2026-15809(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 16× 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.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 13:37 UTCEG score recompute
- 2026-07-17 13:37 UTCGHSA enrichment
- 2026-07-17 02:44 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 14:07 UTCGHSA enrichment
- 2026-07-16 01:31 UTCGHSA enrichment
- 2026-07-15 12:54 UTCEG score recompute
- 2026-07-15 12:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-134
Frequently asked(5)
What is CVE-2026-15809?
When was CVE-2026-15809 disclosed?
Is CVE-2026-15809 actively exploited?
What is the CVSS score of CVE-2026-15809?
How do I remediate CVE-2026-15809?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15809
Is Your Infrastructure Affected by CVE-2026-15809?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.