cve.bz

CVE-2026-104115 omnios omnios: Stack-based Buffer Overflow

5.4 mediumEPSS 0.1%Fix available

Medium (5.4) in omnios omnios. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

5.4 medium
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
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • OmniOS OmniOS: fixed in r151058w
  • OmniOS OmniOS: fixed in r151056aw
  • OmniOS OmniOS: fixed in r151054bw

Ask an AI about this CVE

Show the promptExplain CVE-2026-104115 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104115?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104115?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104115 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OmniOSfrom any before r151054
OmniOSfrom r151058 before r151058w
OmniOSfrom r151056 before r151056aw
OmniOSfrom r151054 before r151054bw

Fixed in

ProductFixed in
OmniOSr151058w
OmniOSr151056aw
OmniOSr151054bw

References

Check your stackJSON