Read the docs

Race condition in Kunai mount namespace cache misattributes events

Priority LOW 8CWE-20Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Kunai versions from 0 through 0.6.2 have a time-of-check to time-of-use race condition (CWE-367) in mount namespace caching. Switcher::new caches a namespace under the expected key without verifying that it matches, so a local user with low privileges can cause a host namespace to be cached for container processes. Security events then resolve against host paths, misattributing container and host activity.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
kunai-projectKunaiup to 0.6.2—No fix listedCNA
  • Kunai Vendorkunai-project Affected up to 0.6.2 Fixed in — No fix listed CNA

CPE names CNA · 1

CPEVersionsRoleVendor
cpe:2.3:a:kunai-project:kunai:*:*:*:*:*:*:*:*———
  • cpe:2.3:a:kunai-project:kunai:*:*:*:*:*:*:*:* Versions — — ·—

Remediation

The sources list no fixed version for Kunai.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-129919
  2. 2026-11-16 CISA SSVC decision points changed
  3. 2026-11-16 Alias added: GHSA-7cjq-6rv3-2w86

References

Sources