# CVE-2026-79417: Race condition in n/a

> Local attackers can cause denial of service in ArgusMonitor.sys via a race condition in device handle access checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-q22r-qwfg-76wv

## What is CVE-2026-79417?

CVE-2026-79417 is a medium-severity vulnerability in n/a, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Access Control in ArgusMonitor.sys in Argotronic eGbR ArgusMonitor 7.4.02 and earlier allows local, low-privileged users to bypass device handle access restrictions via a TOCTOU condition in IRP_MJ_CREATE and send a crafted IOCTL 0x9C4024A8 request, causing denial-of-service.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-79417?


## How do I fix CVE-2026-79417?

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

## Is CVE-2026-79417 being exploited?

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

Public exploit code:

- CVE-2026-79417 PoC (github_poc): https://github.com/connorjaydunn/CVE-2026-79417

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79417 is a medium-severity vulnerability in n/a, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79417 in the wild and no public exploit code.

Affected product: n/a. 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-79417/ (Markdown: https://insights.sbomify.com/CVE-2026-79417/index.md)
```

## Sources

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

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