CVE-2026-70898 Oracle Corporation CVE debrief

Who should care

Organizations using Oracle Hyperion Data Relationship Management should be aware of this vulnerability and take necessary actions to protect their systems. This includes verifying the affected version, reviewing security configurations, and implementing defensive measures such as monitoring for suspicious activity and restricting network access to the affected system. Security teams should prioritize patching and vulnerability management for this product.

Technical summary

The Oracle Hyperion Data Relationship Management product has a vulnerability in the Access and security component. The supported version that is affected is 11.2.25.0.000. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hyperion Data Relationship Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hyperion Data Relationship Management accessible data as well as unauthorized access to critical data or complete access to all Oracle Hyperion Data Relationship Management accessible data.

Defensive priority

High priority due to potential for unauthorized creation, deletion, or modification access to critical data.

Recommended defensive actions

• Verify and apply Oracle Hyperion Data Relationship Management patches
• Restrict network access to the affected system
• Monitor for suspicious activity
• Review and update security configurations
• Perform vulnerability scanning
• Implement compensating controls
• Track exceptions and retest remediated assets

Evidence notes

Evidence from official sources indicates a vulnerability in Oracle Hyperion Data Relationship Management, but details are limited. Further verification is recommended. The CVE record was published on 2026-08-18T21:17:47.470Z and has not been modified since then. Organizations should verify the affected version 11.2.25.0.000 and review security configurations. Defensive measures should include monitoring for suspicious activity and restricting network access to the affected system.

Sources and references

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.