Quick answers
- Is CVE-2026-104115 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104115 being exploited in the wild.
- How severe is CVE-2026-104115?
- Informational severity, published 9 October 2026.
- Which products and versions are affected?
- Illumos prior to illumos-gate commit 6a2df4aa.
- Is there a fix for CVE-2026-104115?
- A patch was published on 2026-10-09: fix available in illumos-gate commit 6a2df4aa Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104115 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-104115?
- Check whether you run Illumos at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow exists in get_fs_locations() within the nfs-basic reparse plugin (libnfs_basic.c), where host and path components from a reparse string are copied into a fixed 1024-byte stack buffer without length validation. The reparsed door at /var/run/reparsed_door is world-readable and performs no credential checking, allowing any local user to send an overlong host or path component to trigger the overflow. On systems with stack protection (the default), this causes reparsed to abort; repeated requests exhaust the service.
Affected products
- illumos illumos prior to illumos-gate commit 6a2df4aa
Timeline
- 2009: other: vulnerability introduced in illumos-gate commit 2f172c55
- 2026-10-09: disclosed
- 2026-10-09: patched: fix available in illumos-gate commit 6a2df4aa