CVE-2026-129919: Kunai, a security monitoring tool, contains a time-of-check to time-of-use (TOCTOU) race condition
Source GCVE Database
Not known to be exploited · CVSS 2.0 Low.
Data as of 16 Nov 2026, 17:21 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 2.0 |
|---|
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| kunai-projectKunai | Affected
| Fixed in– |
GitHubKunaipkg:github/KunaiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability requires local access and precise timing, restricting local access to trusted users and processes can reduce risk. Monitor vendor advisories for any future patches or updates addressing this issue. Until a fix is available, be cautious interpreting container security events from Kunai, as they may be affected by this race condition.
Description
Kunai, a security monitoring tool, has a time-of-check to time-of-use (TOCTOU) race condition in its mount namespace caching logic. This flaw allows an attacker with local access to cause Kunai to cache incorrect mount namespace information by exploiting a timing window when resolving process namespaces. As a result, container security events may be incorrectly resolved against host filesystem paths, undermining the integrity of security monitoring data and potentially allowing attackers to obscure malicious container activity or generate misleading alerts. The vulnerability requires local access and precise timing, with no remote attack vector or user interaction needed. The CVSS score is low, reflecting the limited attack surface and complexity.