On this page (7 sections)
CVE-2026-114784 is a critical vulnerability in the Platform Security component of Oracle Business Intelligence Enterprise Edition, part of Oracle Analytics. According to the GitHub Advisory Database entry, an unauthenticated attacker with network access over HTTP could take over the product. The CVSS 3.1 base score is 10.0, the maximum.
If you run Oracle BI Enterprise Edition 8.2.0.0.0 or 26.01.0.0.0, especially with the web interface reachable from outside your network, this deserves prompt attention. Details are still limited, so this article separates what is confirmed from what is not.
What was disclosed
The record was published by the National Vulnerability Database on November 17, 2026 and added to the GitHub Advisory Database a day later. The description says the flaw is in the Platform Security component, is easily exploitable, and needs no login and no user interaction. Successful attacks can result in takeover of Oracle Business Intelligence Enterprise Edition.
The description also notes a scope change: although the weakness is in BI Enterprise Edition, attacks may significantly impact additional products. In practice, that means a compromised BI server could expose or affect systems it connects to, such as data sources and other components in the same deployment. The sources do not name specific downstream products.
The vendor reference is Oracle's security alert page. The NVD entry repeats the same description, so it is not independent confirmation. GitHub marks its own advisory as unreviewed.
What the CVSS metrics mean
The vector tells you why this scores 10.0. Each element is taken from the published CVSS 3.1 metrics.
| Metric | Value | Plain meaning |
|---|---|---|
| Attack vector | Network | Reachable remotely over HTTP |
| Attack complexity | Low | No special conditions needed |
| Privileges required | None | No account needed |
| User interaction | None | No one has to click anything |
| Scope | Changed | Impact can extend beyond BI itself |
| Confidentiality / Integrity / Availability | High / High / High | Full impact on all three |
The weakness class (CWE) is not listed, and no technical root cause has been published in the sources. Treat any claim about how the flaw works as speculation until Oracle or researchers say more.
Who is realistically exposed
- Organizations running Oracle BI Enterprise Edition 8.2.0.0.0 or 26.01.0.0.0. Other versions are not listed as affected in the sources, but confirm that against Oracle's alert rather than assuming.
- Deployments where the BI web interface is reachable from the internet, a partner network or a flat internal network. The attack path is HTTP, so reachability is the key exposure factor.
- Environments where the BI server holds credentials or connections to databases and other applications, because of the scope change.
How to check your exposure
First identify every BI instance and its version. Use your Oracle documentation or admin console to read the installed version, and compare it with the affected versions above. If you manage a software inventory, search it for Oracle Analytics and Business Intelligence entries.
Next, check what can reach the BI HTTP listener. From a host outside your trusted network, test whether the BI URL answers. This read-only request only shows whether the service responds and what status code it returns. Replace the placeholder with your own BI host name and use only systems you own.
curl -sS -I https://bi.example.com/A response from an external vantage point means the service is exposed and should be prioritized. No response suggests network controls are already limiting access, though that does not replace patching.
What to do now
- Inventory all Oracle BI Enterprise Edition instances and record their versions.
- Open Oracle's security alert for this CVE and find the patch or fix instructions for 8.2.0.0.0 and 26.01.0.0.0.
- Schedule the patch as an emergency change for any instance reachable from the internet; test it first if you have a staging copy.
- Until patched, restrict access to the BI HTTP listener to trusted networks or a VPN, using your firewall or reverse proxy.
- Review BI web server and application logs since mid-November 2026 for unexpected requests, new admin accounts or configuration changes.
- If you see signs of compromise, rotate credentials stored in or used by the BI server, including data source connections.
- Confirm patched versions after the update and re-test external reachability.
Detection and monitoring
No indicators of compromise, exploit patterns or in-the-wild reports are given in the research, so there is no reliable signature to hunt for. Focus on general signals: unusual unauthenticated HTTP requests to the BI host, spikes in errors, unexpected processes on the BI server, and outbound connections from it to unfamiliar destinations.
Watch for changes at the edge too. Unexpected certificate, DNS or response-header changes on your BI host name can indicate tampering, and Webforta Monitor can alert on those. For background on layered protection, see what a WAF is, though a firewall rule is no substitute for the vendor patch.
What is still unknown
- Fixed versions and patch identifiers are not stated in the sources reviewed.
- Exploitation status is unconfirmed; no source reports attacks, and no CISA KEV listing appears in the data.
- No technical root cause, CWE or proof of concept is published.
- Only one independent record (the GitHub advisory, repeated by NVD) covers this so far, and GitHub marks it unreviewed.
We will update this article if Oracle or researchers publish more detail. For other security news and analysis, browse the Webforta blog.
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.
