CVE-2026-15809General

LOWCVSS 7.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-134CWE-116

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • General: 1 classified signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-08-17: 108-17
Signal classification1 categories
General
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • u2usvc@u2usvc
    General

    How to make your CVE DB submission less confusing? (Kubernetes mentioned 0_0) https://u2usvc.xyz/posts/cve-2026-15809/

    Post summary

    The post appears to be a discussion about simplifying CVE database submissions, referencing Kubernetes and CVE-2026-15809, but it does not provide any specific exploit, patch, or technical details.

    00000109
    27 followersView on X

Explore more