On this page (7 sections)

CVE-2026-115089 is a critical vulnerability in the Application Development Framework component of Oracle Hyperion Planning. According to the NVD record, published on 2026-11-17, an unauthenticated attacker with network access over HTTP can compromise the product, and a successful attack can result in takeover of Hyperion Planning.

If you run Hyperion Planning for budgeting and forecasting, or host it for a client, this is worth checking today. The record names one affected version, and the CVSS score is 9.8. Only limited information is public so far, so this article separates what is confirmed from what is not.

What was disclosed

The NVD entry describes an easily exploitable flaw that needs no credentials and no user interaction. The attacker only needs network access to the application over HTTP. The listed impact is high for confidentiality, integrity and availability, which is why the score reaches 9.8.

The only reference attached to the CVE is an Oracle security alert page, cspunov2026. The research does not include the contents of that page, so this article does not state a fixed version or patch number. Read Oracle's advisory directly for the exact patch to apply.

Technical details in plain terms

The record maps the issue to CWE-306, missing authentication for a critical function. In practice this means some functionality in the application can be reached and used without proving who you are. When that functionality is powerful enough, an outsider can do what an administrator would normally do.

The CVSS vector in the record is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Read it as follows:

  • AV:N - reachable over the network, no local access needed.
  • AC:L - low attack complexity, no special conditions.
  • PR:N and UI:N - no privileges and no user action required.
  • C:H, I:H, A:H - high impact on data confidentiality, data integrity and availability.

The research does not describe which endpoint or function is affected, and no exploit details are given. Treat any claims about specific attack paths from other places as unconfirmed unless Oracle states them.

Who is realistically exposed

Only the version listed in the record, 11.2.26.0.000, is named as affected. Hyperion Planning is an internal finance system in most organizations, so the real risk depends on how it is published:

  • Instances reachable from the internet, for example through a reverse proxy or remote access without a VPN for finance teams, carry the highest risk.
  • Instances reachable only from an internal network are still exposed to anyone who gets a foothold inside, such as through a compromised workstation or a vendor connection.
  • Hosted or managed deployments run by a third party may be affected too. Ask your provider which version they run and when they plan to patch.

If you run other Oracle products, check each one against Oracle's own advisories, since this record covers only Hyperion Planning. For general guidance on keeping business systems and sites in good shape, see our small business website security guide.

How to check your exposure

Start with an inventory question: do you run Hyperion Planning, and which version? Your Oracle Enterprise Manager, Hyperion Lifecycle Management or deployment documentation should show the installed release. Compare it with 11.2.26.0.000.

Then check reachability. From a machine outside your corporate network, confirm whether the Hyperion Planning web address responds at all. If it does, it is internet-facing and should be treated as urgent.

Review web server and application logs for unusual unauthenticated requests to Hyperion paths, especially from unfamiliar IP addresses, and for new accounts, changed roles or unexpected configuration changes since the record was published. The research does not list specific indicators, so this is general hygiene, not a confirmed detection signature.

What to do now

  1. Find every Oracle Hyperion Planning instance and record its version, including test and staging systems.
  2. Open Oracle's advisory at oracle.com/security-alerts/cspunov2026.html and identify the patch that covers CVE-2026-115089.
  3. Schedule and apply the patch, starting with instances reachable from the internet. Test in a non-production copy first if you can.
  4. Until patched, restrict network access to Hyperion Planning with firewall rules or a VPN so only the finance users and admins who need it can reach it over HTTP.
  5. Review logs and administrator accounts for unexpected activity since 2026-11-17, and rotate credentials and service account secrets if you see anything suspicious.
  6. Make sure you have a recent, tested backup of the Planning application and its repository before and after patching.
  7. Ask any managed service provider that runs Hyperion for you to confirm their version and patch date in writing.
Caution. Patching an enterprise application usually requires a service restart and a maintenance window. Plan the change with the finance team, and do not apply it to production without a rollback plan.

Monitoring after the fix

A critical, unauthenticated flaw is a good reason to keep watching after you patch. Track Oracle's advisory page for updates, and watch for changes in public reporting about exploitation. The research notes that only one independent publisher covers this story so far, and it lists no CISA Known Exploited Vulnerabilities entry for the CVE, so the picture may change.

For any public-facing web address in front of the application, keep an eye on certificate expiry, DNS changes and unexpected header changes. Webforta Monitor can watch those for sites you verify, and the free SSL checker gives a quick look at a certificate. These help you notice changes around the system but do not tell you whether this particular flaw is present.

If you suspect a system was already accessed, follow our guide on what to do when a website is hacked.

What is still unknown

  • The fixed version or patch identifier is not stated in the research.
  • No exploit activity, proof of concept or attacker attribution is reported.
  • The specific vulnerable function or endpoint is not described.
  • Only one independent publisher is covering this so far, and the technical facts come from the NVD record.

Treat the 9.8 score and the no-authentication description as reason enough to act without waiting for more detail.

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-115089: Vulnerability in the Oracle Hyperion Planning product of Oracle Hyperion (component: Application Development Framework).nvd.nist.gov ·
  • Oracle
  • Hyperion
  • CVE-2026-115089
  • Critical vulnerability
  • CWE-306