CVE-2026-70741: Vulnerability in the Oracle Hyperion Financial Reporting product of Oracle Hyperion (component: Server).
Vulnerability in the Oracle Hyperion Financial Reporting product of Oracle Hyperion (component: Server). The supported version that is affected is 11.2.25.0.000. Easily exploitable vulnerability allows unauthenticated attacker with network access via RMI to compromise Oracle Hyperion Financial Reporting. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hyperion Financial Reporting accessible data as well as unauthorized access to critical data or complete access to all Oracle Hyperion Financial Reporting accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
Security readout for executives and security teams
Plain-English summary
Oracle Hyperion Financial Reporting 11.2.25.0.000 contains a critical access-control vulnerability. An unauthenticated attacker who can reach its RMI service may read, create, delete, or modify critical reporting data. Availability impact is not identified, but compromise of financial information could undermine confidentiality, reporting integrity, and business decisions.
Executive priority
Treat this as an urgent remediation item for affected, RMI-reachable systems. Prioritize externally or broadly reachable deployments and those supporting material financial reporting. The principal business risk is unauthorized disclosure or manipulation of critical data, potentially affecting reporting confidence and downstream decisions.
Technical view
CVE-2026-70741 is a CWE-284 access-control weakness in the Oracle Hyperion Financial Reporting Server component. It is remotely and easily exploitable through network-accessible RMI without privileges or user interaction. The CVSS 3.1 score is 9.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
Likely exposure
Exposure is supported only for Oracle Hyperion Financial Reporting version 11.2.25.0.000. Risk is greatest where its RMI service is reachable from untrusted networks. The supplied sources do not identify other affected versions, deployment configurations, ports, or products.
Exploitation context
The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or public exploit availability. That does not establish that exploitation has never occurred. The described attack requires network access to RMI but no authentication, privileges, or victim interaction.
Researcher notes
The available record identifies the Server component, RMI attack path, affected version, and high confidentiality and integrity impacts. It does not describe the underlying access-control failure, vulnerable method, affected port, patch identifier, detection indicators, or exploit availability. Validation should remain configuration- and evidence-based until Oracle publishes further technical detail.
Mitigation direction
Identify Oracle Hyperion Financial Reporting 11.2.25.0.000 installations and their owners.
Check Oracle's August 2026 Critical Patch Update for the prescribed update or mitigation.
Restrict RMI access to explicitly authorized management and application networks.
Prioritize systems containing sensitive financial or regulatory reporting data.
Monitor Oracle guidance for clarifications about affected configurations and remediation.
Validation and detection
Confirm installed Hyperion Financial Reporting versions using approved inventory records.
Map which networks and identities can reach each server's RMI service.
Verify Oracle's prescribed remediation is applied to every affected instance.
Review access and change logs for unexplained reporting-data access or modification.
Reassess RMI exposure after remediation and document any accepted exceptions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.