Skip to content
ERP

CVE-2026-70892

8.2
High
EPSS 0.24%Patch availableAug 19, 2026

Oracle Hyperion DRM 11.2.25 allows low-privileged remote actors to modify or access critical data.

common questions

Is CVE-2026-70892 being exploited?

Not confirmed. CVE-2026-70892 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-70892?

CVE-2026-70892 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-70892?

Yes. A fix has been recorded for CVE-2026-70892. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-70892 affect?

CVE-2026-70892 affects Oracle Hyperion Data Relationship Management 11.2.25.0.000, Oracle Hyperion family (potential scope change). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70892?

Apply vendor patch/mitigations; restrict HTTP access to DRM; enforce least privilege; monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle Hyperion Data Relationship Management 11.2.25.0.000Oracle Hyperion family (potential scope change)
impact

Low-priv attacker via HTTP can create, delete, or modify critical DRM data, causing full confidentiality and integrity loss of accessible data.

action required

Patch when possible

affected versions
Oracle Corporation Oracle Hyperion Data Relationship Management
  • affected11.2.25.0.000

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free