CVE-2026-15809

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
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 computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 15, 2026

Last Modified

September 17, 2026

Advisory Details (5)

Auto-updated Jul 15, 2026
Patch available. Sources: github_pr, redhat.
github_pr

[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/6524
github_pr Patch Available

server: 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/6450
redhat

2500846 – (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=2500846
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/cve-2022-4318
redhat Patch Available

cve-details

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

Vendor Advisories for CVE-2026-15809(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcri-o-0:1.25.5-36.rhaos4.12.git2e7f657.el82026-09-17redhat
redhatcri-o-0:1.26.5-32.rhaos4.13.git1088e36.el82026-09-17redhat
redhatcri-o-0:1.31.13-14.rhaos4.18.gitf2de9ac.el82026-09-17redhat
redhatcri-o-0:1.29.13-14.rhaos4.16.git84cfdc6.el82026-09-10redhat
redhatcri-o-0:1.32.13-11.rhaos4.19.git089e95c.el92026-09-02redhat
redhatcri-o-0:1.33.13-5.rhaos4.20.git7ebc848.el92026-09-01redhat
redhatcri-o-0:1.34.11-4.rhaos4.21.git358c4b4.el92026-09-01redhat
redhatcri-o-0:1.35.6-5.rhaos4.22.git41f610b.el92026-08-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 120× 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.

Showing the most recent 100 of 230 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-18 04:46 UTCEG score recompute
  3. 2026-09-18 04:46 UTCVendor advisory
  4. 2026-09-18 04:46 UTCGHSA enrichment
  5. 2026-09-17 12:19 UTCEG score recompute
  6. 2026-09-17 12:19 UTCVendor advisory
  7. 2026-09-17 12:19 UTCGHSA enrichment
  8. 2026-09-17 11:49 UTCEG score recompute
  9. 2026-09-17 11:49 UTCVendor advisory
  10. 2026-09-17 11:49 UTCGHSA enrichment
  11. 2026-09-17 09:32 UTCEG score recompute
  12. 2026-09-17 09:32 UTCVendor advisory
  13. 2026-09-17 09:32 UTCGHSA enrichment
  14. 2026-09-17 08:35 UTCEG score recompute
  15. 2026-09-17 08:35 UTCVendor advisory
  16. 2026-09-17 08:35 UTCGHSA enrichment
  17. 2026-09-16 14:07 UTCEPSS rescore
  18. 2026-09-16 05:14 UTCEPSS rescore
  19. 2026-09-13 23:13 UTCEG score recompute
  20. 2026-09-13 23:13 UTCVendor advisory
  21. 2026-09-13 23:13 UTCGHSA enrichment
  22. 2026-09-13 16:46 UTCEPSS rescore
  23. 2026-09-13 07:16 UTCEG score recompute
  24. 2026-09-13 07:16 UTCVendor advisory
  25. 2026-09-13 07:16 UTCGHSA enrichment
Show 75 more
  1. 2026-09-12 15:00 UTCEPSS rescore
  2. 2026-09-12 13:03 UTCVendor advisory
  3. 2026-09-12 13:03 UTCGHSA enrichment
  4. 2026-09-11 21:47 UTCEG score recompute
  5. 2026-09-11 21:47 UTCVendor advisory
  6. 2026-09-11 21:47 UTCGHSA enrichment
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:36 UTCEPSS rescore
  9. 2026-09-10 10:38 UTCEG score recompute
  10. 2026-09-10 10:38 UTCVendor advisory
  11. 2026-09-10 10:38 UTCGHSA enrichment
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-10 09:32 UTCEG score recompute
  14. 2026-09-10 09:32 UTCVendor advisory
  15. 2026-09-10 09:32 UTCGHSA enrichment
  16. 2026-09-08 22:00 UTCEPSS rescore
  17. 2026-09-08 00:56 UTCEG score recompute
  18. 2026-09-08 00:56 UTCVendor advisory
  19. 2026-09-08 00:56 UTCGHSA enrichment
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-06 13:29 UTCVendor advisory
  23. 2026-09-06 13:29 UTCGHSA enrichment
  24. 2026-09-05 20:52 UTCEG score recompute
  25. 2026-09-05 20:52 UTCVendor advisory
  26. 2026-09-05 20:51 UTCGHSA enrichment
  27. 2026-09-04 05:06 UTCEPSS rescore
  28. 2026-09-02 20:22 UTCEG score recompute
  29. 2026-09-02 20:22 UTCVendor advisory
  30. 2026-09-02 20:22 UTCGHSA enrichment
  31. 2026-09-02 19:46 UTCEG score recompute
  32. 2026-09-02 19:46 UTCVendor advisory
  33. 2026-09-02 19:46 UTCGHSA enrichment
  34. 2026-09-02 14:11 UTCEPSS rescore
  35. 2026-09-01 20:22 UTCEG score recompute
  36. 2026-09-01 20:22 UTCVendor advisory
  37. 2026-09-01 20:21 UTCGHSA enrichment
  38. 2026-09-01 20:05 UTCEG score recompute
  39. 2026-09-01 20:05 UTCVendor advisory
  40. 2026-09-01 20:04 UTCGHSA enrichment
  41. 2026-09-01 17:23 UTCEG score recompute
  42. 2026-09-01 17:23 UTCVendor advisory
  43. 2026-09-01 17:23 UTCGHSA enrichment
  44. 2026-09-01 17:05 UTCEG score recompute
  45. 2026-09-01 17:05 UTCVendor advisory
  46. 2026-09-01 17:04 UTCGHSA enrichment
  47. 2026-09-01 13:53 UTCEPSS rescore
  48. 2026-09-01 04:39 UTCEPSS rescore
  49. 2026-08-31 05:15 UTCEG score recompute
  50. 2026-08-31 05:15 UTCVendor advisory
  51. 2026-08-31 05:15 UTCGHSA enrichment
  52. 2026-08-30 19:17 UTCEPSS rescore
  53. 2026-08-30 16:30 UTCVendor advisory
  54. 2026-08-30 16:30 UTCGHSA enrichment
  55. 2026-08-30 03:54 UTCEG score recompute
  56. 2026-08-30 03:54 UTCVendor advisory
  57. 2026-08-30 03:54 UTCGHSA enrichment
  58. 2026-08-30 01:22 UTCEPSS rescore
  59. 2026-08-28 21:41 UTCEPSS rescore
  60. 2026-08-28 02:35 UTCEG score recompute
  61. 2026-08-28 02:35 UTCVendor advisory
  62. 2026-08-28 02:35 UTCGHSA enrichment
  63. 2026-08-27 14:25 UTCEPSS rescore
  64. 2026-08-27 13:59 UTCVendor advisory
  65. 2026-08-27 13:59 UTCGHSA enrichment
  66. 2026-08-27 01:23 UTCEG score recompute
  67. 2026-08-27 01:23 UTCVendor advisory
  68. 2026-08-27 01:23 UTCGHSA enrichment
  69. 2026-08-26 14:46 UTCEPSS rescore
  70. 2026-08-26 12:45 UTCVendor advisory
  71. 2026-08-26 12:45 UTCGHSA enrichment
  72. 2026-08-26 00:02 UTCEG score recompute
  73. 2026-08-26 00:02 UTCVendor advisory
  74. 2026-08-26 00:02 UTCGHSA enrichment
  75. 2026-08-25 13:48 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-15809?
CVE-2026-15809 is a high vulnerability published on July 15, 2026. 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…
When was CVE-2026-15809 disclosed?
CVE-2026-15809 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15809 actively exploited?
CVE-2026-15809 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-15809?
CVE-2026-15809 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-15809?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15809, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15809?

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

Start Free Scan →Browse All CVEs