CVE-2026-129919 Kunai Mount Namespace Cache TOCTOU Allows Incorrect Event Resolution Against Host Files

Low 2.0 Published Updated

Local attackers can race Kunai's mount namespace caching so security events are resolved against host files, misleading alerts or hiding malicious activity.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Harmful if only installed
No
Needs a specific call
No
Fix
None listed

What is CVE-2026-129919?

CVE-2026-129919 is a low-severity race condition vulnerability in kunai-project Kunai, published on 16 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-367, CWE-20

Which versions are affected by CVE-2026-129919?

It affects 1 product.

An affected version is exposed as installed. No special setting or call is needed.

Products include Kunai-Project Kunai.

How do I fix CVE-2026-129919?

No fix has been published for CVE-2026-129919 yet. Limit exposure of the affected software until one is available.

Upgrade, and make the check and the action one atomic step. More about Race condition.

Is CVE-2026-129919 being exploited?

There is no known exploitation of CVE-2026-129919 in the wild and no public exploit code.

Sources

Also known as GHSA-7cjq-6rv3-2w86.

Is CVE-2026-129919 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free