Oracle Solaris EUVD-2026-106461

Exploitation is confined to the Oracle Solaris 11.4 'Services' component and requires the attacker to first have local logon access to the infrastructure where Solaris runs (AV:L). It additionally requires human interaction from a person OTHER than the attacker (UI:R) - a separate legitimate user must perform some action for the attack to succeed - and the flaw is rated high complexity (AC:H), implying race conditions, specific timing, or non-trivial preconditions. These three factors (local access, dependence on a second user, and high complexity) are the primary limiters and keep realistic risk well below what a network-facing flaw would carry; impact is bounded to partial unauthorized modification of some Solaris-accessible data, with no confidentiality or availability effect.

This is a genuinely low-priority issue, and the signals align rather than conflict. The CVSS 3.1 base score is 2.5 (Low), driven by a vector of AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N - local attack vector, high attack complexity, no privileges but mandatory user interaction, and a single low-integrity impact with no confidentiality or availability consequence. No EPSS score was provided in the input, the CVE is NOT listed in CISA KEV, and no public proof-of-concept is referenced, so exploitation status is 'no public exploit identified at time of analysis.' The only meaningful real-world outcome per Oracle is unauthorized update/insert/delete access to SOME Solaris-accessible data - a limited integrity effect. Note one internal tension in Oracle's own phrasing: the vector states PR:N (no privileges) yet the description says the attacker needs 'logon to the infrastructure where Oracle Solaris executes,' meaning local presence is required even if no application credentials are - treat the AV:L/UI:R combination, not the PR:N label, as the true access barrier. Bottom line: low CVSS backed by local-only access, high complexity, and a dependency on a separate victim's interaction makes this a low real-world risk, not a hidden priority.

An attacker who already has local logon access to a Solaris 11.4 host crafts a malicious input or file in the Services component and then waits for or socially engineers a separate legitimate user to perform an action that triggers the flaw. Because high complexity and victim interaction are both required, successful exploitation is opportunistic and yields only limited unauthorized modification of some Solaris-accessible data. No public exploit code is known at time of analysis.