Skip to main content

CVE-2026-129919kunai-project Kunai time-of-check to time-of-use race

Low priorityLow2.0EPSS not scored yet

CVE-2026-129919 is a time-of-check to time-of-use race in kunai-project Kunai, rated low (2.0 on CVSS 4.0).

Why this priority: Low severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Something is checked, then changed by an attacker before it is used. The software trusts input it should check, so crafted values reach code that assumes they are well formed.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker win a timing window to bypass a check or corrupt shared state. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place kunai-project Kunai runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

Kunai, a security monitoring tool, contains a time-of-check to time-of-use (TOCTOU) race condition in its mount namespace (mnt ns) caching logic. When resolving a security event that references a specific process PID and an expected mount namespace, the Switcher::new function read /proc/<pid>/ns/mnt to determine the target namespace and cached the result under the expected namespace key without verifying that the resolved namespace actually matched the expected one.

An attacker with local access could exploit this by either (1) arranging for the referenced PID to be reused by a process in a different namespace (e.g., the host namespace) before Kunai resolves it, or (2) calling unshare or setns on the target process after the event is generated but before the namespace is resolved. In either case, the wrong namespace (potentially the host's own namespace) would be cached under the container's namespace key.

The security impact is that subsequent container security events would be resolved against host filesystem paths rather than container paths. This undermines the integrity of the security monitoring data: container activity could be misattributed to the host, host activity could be misattributed to a container, and file-path-based detections or alerts would reference incorrect paths. An attacker could potentially use this to obscure malicious activity within a container by making it appear as benign host activity, or to generate misleading security alerts.

The vulnerability requires local access to the system and a specific timing window between event generation and namespace resolution. No remote attack vector or user interaction is required.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Request handlers and jobs that share state. The flaw sits between concurrent requests or processes.
  • Interfaces that accept external input. The flaw sits at the input boundary of the affected component.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between concurrent requests or processes. An attacker who crosses it can win a timing window to bypass a check or corrupt shared state.
  • At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.

Questions to answer about your own systems

  • Where does kunai-project Kunai run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.