# CVE-2026-104115: Stack buffer overflow in illumos reparsed nfs-basic plugin allows local users to crash the daemon

> A local attacker can crash the illumos reparse daemon by sending an overlong NFS reparse string, causing a denial of service.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gwf6-7hwv-r7vq

## What is CVE-2026-104115?

CVE-2026-104115 is a medium-severity memory corruption vulnerability in OmniOS, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow in the illumos reparse point daemon (reparsed) allows a local user to crash the daemon. get_fs_locations() in usr/src/cmd/fs.d/nfs/rp_basic/libnfs_basic.c, part of the nfs-basic reparse plugin, copies the host and path components of a reparse string into a fixed 1024-byte stack buffer without checking their length. The reparsed door at /var/run/reparsed_door is readable by all users and the door server does not check the caller's credentials, so an unprivileged local user can send an nfs-basic request with an overlong host or path component to overflow the buffer. On systems built with stack protection, which is the default, this causes reparsed to abort; repeated requests place the svc:/system/filesystem/reparse service into maintenance. The service is disabled by default. The flaw has existed since 2009 (illumos-gate commit 2f172c55), and affects any illumos distribution prior to illumos-gate commit 6a2df4aa.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-104115 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104115 is a medium-severity memory corruption vulnerability in OmniOS, published on 9 Oct 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-104115 in the wild and no public exploit code.

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

## Sources

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

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