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

Published Nov 16, 2026
·
Updated

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.

Affected Software

1 affected component
Quarkslab Kunai

Event History

Nov 16, 2026
CVE Published
via MITRE·01:49 PM
Data Sourced
via MITRE·01:49 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What level of access would an attacker need?

The attacker would need local access and the ability to influence the process referenced by a security event. Exploitation relies on either PID reuse before resolution or changing the target process's mount namespace with unshare or setns during the resolution window.

2

What is the practical impact of a successful race?

Kunai can cache an incorrect mount namespace under a container's expected namespace key, potentially caching the host namespace. Later container events may then be resolved using host filesystem paths, undermining the integrity and attribution of monitoring data.

3

Does the issue affect only the initial event involved in the race?

No. Because the incorrectly resolved namespace is cached under the expected container namespace key, subsequent container security events can also be resolved against the wrong filesystem namespace.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203