Oracle Essbase EUVD-2026-106836

Exploitation requires an interactive local logon to the infrastructure where Oracle Essbase 21.8.3.0.0 executes AND high existing privileges on that host (CVSS AV:L, PR:H); it targets the Java Based Agent component. There is no network vector and no user interaction. Limiting factors: the attacker must already be an authenticated, high-privileged local user, which substantially narrows the exploit population to insiders or attackers who have already achieved privileged footholds; impact is confined to confidentiality (no integrity or availability effect), though the scope change means disclosed data may include that of other products on the host.

This is a moderate-severity, local-privilege vulnerability that should be prioritized below internet-facing or unauthenticated flaws. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N, base 6.0) confirms the attacker must already have local logon access to the host running Oracle Essbase AND hold high privileges (PR:H) - so this is a privilege/scope-escalation issue affecting confidentiality only, not a remote entry point. The scope change (S:C) is the aggravating factor: a compromise can reach data in additional products beyond Essbase itself. No EPSS score, KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; this keeps real-world urgency low-to-moderate despite the confidentiality impact. The three signals are consistent (high access barrier, no exploitation intelligence) rather than conflicting. One caveat: the input Tags include 'Authentication Bypass', which directly contradicts the CVSS PR:H / 'high privileged attacker with logon' language - treat that tag as suspect and verify against the Oracle advisory rather than assuming any auth-bypass behavior.

An attacker who already holds a high-privilege local account on the server hosting Oracle Essbase abuses the Java Based Agent component to read confidential data. Because the flaw carries a scope change, the compromise can extend to data managed by other co-located products, not just Essbase. No public exploit code is known, so exploitation would require a bespoke technique and pre-existing privileged access.