On this page (7 sections)

Oracle Hyperion Infrastructure Technology version 11.2.26.0.000 is affected by CVE-2026-115139, a critical vulnerability in the Installation and Configuration component. According to the NVD record, an unauthenticated attacker with network access over HTTP can compromise the product, although a person other than the attacker has to take part in a successful attack.

Three more CVEs were published the same day for the same product and version, two of them scored 9.8. If your organization runs Hyperion Infrastructure Technology, treat this as a patching priority and read Oracle's advisory for fix details, which our sources do not include.

What happened

On 2026-11-17, NVD published four records for Oracle Hyperion Infrastructure Technology, all pointing to Oracle's security alert page. Each says the supported affected version is 11.2.26.0.000, the component is Installation and Configuration, and the issue is easily exploitable by an unauthenticated attacker over HTTP.

This article focuses on CVE-2026-115139, but the siblings matter just as much because they share the same exposure. Only one independent publisher covers this story so far, and the sources here are the NVD records themselves, so details such as patch numbers and exploitation status should be confirmed directly with Oracle.

Technical details of CVE-2026-115139

The record describes the flaw as easily exploitable, needing no privileges and no login, with network access over HTTP. Two traits set it apart from the other three CVEs:

  • Human interaction is required. A person other than the attacker must take part for an attack to succeed (CVSS vector value UI:R).
  • Scope change. The vulnerable component is Hyperion Infrastructure Technology, but NVD says a successful attack may significantly impact additional products (CVSS vector value S:C).
  • Impact is high for confidentiality and integrity, with no availability impact. NVD says attacks can allow unauthorized creation, deletion or modification of critical data, and unauthorized access to critical or all accessible data.

No CWE is listed for this CVE, and the research gives no further technical detail. We will not speculate about the root cause or the interaction involved.

The three related CVEs

Oracle Hyperion Infrastructure Technology 11.2.26.0.000, published 2026-11-17 (NVD)
CVECVSS 3.1User interactionImpact described
CVE-2026-1151399.3Required, scope changedCreate, delete or modify critical data; read critical data
CVE-2026-1150809.8NoneTakeover of the product
CVE-2026-1150479.8NoneTakeover of the product
CVE-2026-1150509.1NoneCreate, delete or modify critical data; read critical data (CWE-284 listed)

Details are in the NVD records for CVE-2026-115080, CVE-2026-115047 and CVE-2026-115050.

Who is affected

Only installations of Oracle Hyperion Infrastructure Technology at version 11.2.26.0.000 are named. Because the attack path is over HTTP with no authentication, the key exposure question is who can reach your Hyperion HTTP services over the network. The research does not say whether other versions are affected or unaffected, so confirm that with Oracle rather than assuming.

How to check your exposure

Start with an inventory. You need to know whether you run this product, which version, and who can reach it over the network.

  • Check your Hyperion installation records or the inventory tooling your team uses to see whether Infrastructure Technology is at 11.2.26.0.000.
  • Identify which hosts serve Hyperion over HTTP or HTTPS and from which networks they are reachable (internet, VPN, partner links, internal only).
  • Review firewall and load balancer rules for those hosts, including any old rules left from installation or migration work.

If you manage an externally visible site and want a quick outside view of what a visitor can see, a read-only security scan of a verified site can help with that inventory. It does not tell you whether this specific flaw is present.

What to do now

  1. Open Oracle's advisory at oracle.com/security-alerts/cspunov2026.html and find the patch instructions for Oracle Hyperion Infrastructure Technology 11.2.26.0.000.
  2. Confirm which Hyperion instances you run and record their exact versions.
  3. Apply the Oracle patch to all affected instances, starting with those reachable from outside the internal network. Test in staging first where you can.
  4. If you cannot patch immediately, restrict network access to the Hyperion HTTP endpoints to the smallest set of trusted hosts or VPN users.
  5. Optionally, put a reverse proxy or web application firewall in front of Hyperion as general hardening. The research does not show that this protects against these CVEs, so it is not a substitute for patching.
  6. Review web server and application logs on Hyperion hosts for unexpected HTTP requests and escalate anything unusual.
  7. Remind administrative users to be cautious with unexpected links or prompts that point to Hyperion, since CVE-2026-115139 requires another person's involvement. The research does not say what that involvement is.
Caution. Applying patches to an enterprise platform can require downtime and restarts of services. Schedule a maintenance window, take backups and follow Oracle's instructions exactly.

Detection and monitoring

The research reports no exploitation and no CISA KEV listing as of the sources. That reflects the sources at the time of writing, so re-check Oracle's advisory and the CISA catalog periodically. After patching, keep watching:

  • Web and application logs on Hyperion hosts for unusual HTTP requests, especially from external addresses.
  • Unexpected changes to data or configuration, which would match the integrity impact described.
  • Whether the Hyperion host is still reachable from networks it should not be. Certificate, DNS and uptime monitoring on externally visible hostnames can flag unexpected changes.

If you suspect compromise, follow the steps in website hacked: what to do, adapted to your internal incident process.

What we do not know yet

  • The fixed version or patch identifier is not given in the sources we reviewed.
  • No public exploit, proof of concept or in-the-wild attack is reported in the research.
  • The specific user interaction needed for CVE-2026-115139 is not described.
  • Whether versions other than 11.2.26.0.000 are affected is not stated.

We will treat any of these as unknown until Oracle or another primary source says otherwise.

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-115139: Vulnerability in the Oracle Hyperion Infrastructure Technology product of Oracle Hyperion (component: Installation and Configuration).nvd.nist.gov ·
  2. CVE-2026-115080: Vulnerability in the Oracle Hyperion Infrastructure Technology product of Oracle Hyperion (component: Installation and Configuration).nvd.nist.gov ·
  3. CVE-2026-115050: Vulnerability in the Oracle Hyperion Infrastructure Technology product of Oracle Hyperion (component: Installation and Configuration).nvd.nist.gov ·
  4. CVE-2026-115047: Vulnerability in the Oracle Hyperion Infrastructure Technology product of Oracle Hyperion (component: Installation and Configuration).nvd.nist.gov ·
  • Oracle
  • Hyperion
  • CVE-2026-115139
  • critical vulnerability
  • patch management