PatchSiren cyber security CVE debrief
CVE-2026-91654 Oracle CVE debrief
A vulnerability in Oracle Essbase allows low-privileged attackers with network access via HTTP to compromise the system, potentially leading to unauthorized data access and partial denial of service. This vulnerability affects Oracle Essbase version 21.8.3.0.0 and has a CVSS score of 6.3, indicating a medium severity level. The vulnerability can allow unauthorized update, insert or delete access to some of Oracle Essbase accessible data as well as unauthorized read access to a subset of Oracle Essbase accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Essbase.
- Vendor
- Oracle
- Product
- Essbase
- CVSS
- MEDIUM 6.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-20
- Original CVE updated
- 2026-10-27
- Advisory published
- 2026-10-20
- Advisory updated
- 2026-10-27
Who should care
Oracle Essbase administrators and security teams should assess exposure and prioritize remediation. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Why it matters
Defenders should care about CVE-2026-91654 because it allows low-privileged attackers to compromise Oracle Essbase, potentially leading to unauthorized data access and partial denial of service. Oracle Essbase administrators and security teams should assess exposure and prioritize remediation. The vulnerability has a CVSS score of 6.3, indicating a medium severity level. However, the actual impact and exploitation status require verification from official sources.
- Potential unauthorized data access
- Potential partial denial of service
- Need for patch verification and application
- Potential for compromised system configurations
Technical summary
The vulnerability in Oracle Essbase has a CVSS score of 6.3 and can allow low-privileged attackers with network access via HTTP to compromise the system, potentially leading to unauthorized update, insert or delete access to some of Oracle Essbase accessible data as well as unauthorized read access to a subset of Oracle Essbase accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Essbase.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the vendor's security patch
- Restrict network access to Oracle Essbase
- Monitor for suspicious activity
- Verify system configurations and user privileges
- Conduct a thorough review of the system to identify potential vulnerabilities
- Implement compensating controls for exposed systems while remediation is scheduled and verified
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and potential impacts. The vulnerability has been identified in Oracle Essbase version 21.8.3.0.0. The CVSS vector is (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L). Defenders should verify the affected scope and apply patches or mitigations accordingly.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-91654 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-91654
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-91654 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-91654
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cpuoct2026.html
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.