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

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

- **Severity:** Low 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:N`)
- **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 available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-7cjq-6rv3-2w86

## 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 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-20 (Improper Input Validation)

## 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: Kunai-Project Kunai.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:kunai-project:kunai:*:*:*:*:*:*:*:*` up to 0.6.2

## 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.

## Is CVE-2026-129919 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129919 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-129919 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: kunai-project Kunai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129919/ (Markdown: https://insights.sbomify.com/CVE-2026-129919/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129919
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129919
- OSV: https://osv.dev/vulnerability/CVE-2026-129919

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129919/
Summaries are generated and may contain mistakes; the official description above is the record.
