On this page (7 sections)

Oracle Hyperion Planning, a corporate budgeting and planning product, has a critical flaw tracked as CVE-2026-115086. According to the NVD record, an unauthenticated attacker with network access over RMI (Java Remote Method Invocation) can compromise the product, and a successful attack can result in takeover of Hyperion Planning.

If you run Hyperion Planning, or host it for a client, this is worth checking today. The research available so far is limited to the CVE records, so this article separates what is confirmed from what is not yet known.

What was disclosed

The CVE was published on 2026-11-17. The record describes an easily exploitable weakness in the Security component of Oracle Hyperion Planning. The only affected supported version named is 11.2.26.0.000. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, which means network reachable, low complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability.

The only reference attached to the record is Oracle's security alert page. The research does not include the text of that page, so fixed versions, patch identifiers and any workarounds are not confirmed here. Read the Oracle page directly before planning your update.

Only one independent publisher covers this story so far, and the NVD description is the main source. No exploitation reports, proof-of-concept code or attacker activity are mentioned in the research. Treat exploitation status as unknown, not as safe.

Why an unauthenticated RMI flaw matters

RMI is a Java mechanism that lets one program call methods on objects in another process over the network. It is normally meant for internal service-to-service traffic. When an RMI endpoint is reachable by someone who has not logged in, any weakness in how it checks requests becomes remotely usable. The record gives no technical root cause, and this article will not speculate on one.

What the record does say is enough to rate the risk. A score of 9.8 with no privileges and no user interaction means the main barrier is network reachability. An attacker who can reach the RMI service may not need credentials, a phishing click or an insider.

Who is realistically exposed

  • Organizations running Hyperion Planning 11.2.26.0.000, typically finance and planning teams on self-managed or hosted Oracle EPM stacks.
  • Environments where RMI ports are reachable from broad internal networks, partner links, VPN pools or the internet.
  • Agencies and hosting providers that run Hyperion on behalf of clients and may not have it in their normal patching inventory.

The record names only version 11.2.26.0.000 as affected. It does not say whether other versions are safe, so confirm with Oracle rather than assuming.

How to check your exposure

Start with inventory, then network reachability. Neither requires touching the application itself.

  1. Find every Hyperion Planning instance, including test, staging and disaster recovery copies, and note the installed version from your Oracle EPM administration console or deployment records.
  2. Compare against the affected version in the record (11.2.26.0.000) and the guidance on Oracle's advisory page.
  3. Ask your network team which hosts and networks can reach the Hyperion Planning servers, and on which ports, particularly RMI-related ports in your deployment.
  4. Check firewall and security group rules for any rule that exposes those ports to the internet or to wide internal ranges.

On a Linux host, the command below lists listening TCP sockets together with the owning process. It is read-only. Run it on the Planning server (as root to see process names) and look for Java processes listening on addresses other than loopback, then compare those ports with your firewall rules.

List listening TCP sockets and their processes (Linux, run on the server)Shell
ss -ltnp

What to do now

  1. Open Oracle's security alert page and find the fix for CVE-2026-115086.
  2. Schedule the Oracle-provided update for every Hyperion Planning 11.2.26.0.000 instance, production first.
  3. Until patched, restrict network access to the Planning servers so only required application and administration hosts can reach them.
  4. Make sure RMI-related ports are not exposed to the internet or untrusted networks.
  5. Review authentication, application and network logs on the Planning servers for unexpected connections since the CVE was published on 2026-11-17 and earlier where logs allow.
  6. If you find any sign of unexpected access, rotate credentials and service accounts used by Hyperion Planning.
  7. Record the patched version in your asset inventory so the next advisory is easy to match.
Caution. Applying Oracle patches usually means restarting Hyperion services and can interrupt planning cycles. Test in a non-production copy and schedule a maintenance window, but do not let testing delay the fix for an internet-reachable system.

A second Hyperion Planning flaw published the same day

A second CVE, CVE-2026-114956, was published the same day and references the same Oracle page. It is also a Security component flaw in Hyperion Planning 11.2.26.0.000. It is reachable over HTTP, requires a person other than the attacker to take an action, and has a scope change. Its CVSS 3.1 base score is 9.3, and its impact is on confidentiality and integrity, not availability.

Oracle's advisory page may list further Hyperion fixes, so review it in full and handle everything that applies to your deployment in the same maintenance pass.

Detection and monitoring afterwards

  • Alert on new or unusual inbound connections to Hyperion servers from hosts that do not normally talk to them.
  • Watch for new accounts, changed roles or unexpected configuration changes in Hyperion Planning.
  • Keep an eye on Oracle's security alerts and subscribe to them so critical records reach you quickly.
  • For any public-facing web components in front of Hyperion, a security scan of the sites you control and monitoring of certificates, DNS and headers can show unexpected exposure changes, though they cannot see inside an internal RMI service.

For general guidance on responding if you suspect compromise, see website hacked: what to do.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-115086: Vulnerability in the Oracle Hyperion Planning product of Oracle Hyperion (component: Security).nvd.nist.gov ·
  2. CVE-2026-114956: Vulnerability in the Oracle Hyperion Planning product of Oracle Hyperion (component: Security).nvd.nist.gov ·
  • Oracle
  • Hyperion
  • CVE-2026-115086
  • RMI
  • critical vulnerability