Skip to content
Security & Trust

Horizon3: two Oracle ERP flaws chain into takeover with no login; patch is the fix

Horizon3 says CVE-2026-114924 and CVE-2026-114925 together let an unauthenticated attacker run commands on the application server

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
Horizon3: two Oracle ERP flaws chain into takeover with no login; patch is the fix
In brief
  • Horizon3 says two Oracle E-Business Suite flaws, CVE-2026-114924 and CVE-2026-114925, can be combined to run commands on the application server without a login.
  • Oracle's advisory lists no workaround and does not report exploitation in the wild. The November 2026 patch is the fix, and internet exposure is not required for an attack.
  • Leaders should confirm the patch status of every EBS 12.2 system and map which internal, partner and supplier networks can reach it.

A network boundary is not a lock

Many companies try to protect a key business system by keeping it off the internet. Horizon3.ai's analysis of two new Oracle flaws shows how little that can cover. ERP systems typically hold finance, purchasing and payroll records. Which parts of your own network can reach yours?

Horizon3's attack researchers describe two flaws in Oracle E-Business Suite. This is Oracle's ERP platform, which companies run on their own servers. The flaws are CVE-2026-114924 and CVE-2026-114925. Oracle scores each 9.8 out of 10 on the CVSS v3.1 scale.

Horizon3 says the two can be linked. An attacker with no credentials, working from afar, could then run operating system commands on the application tier. The attack travels over ordinary web traffic, called HTTP.

What the two flaws do

The first flaw, CVE-2026-114924, is an authorization bypass. It is in the Core part of Oracle Application Object Library. That library is the shared layer that decides who may use which function across E-Business Suite modules.

Horizon3 says specially built web requests can slip past those checks. They then reach protected REST functions. REST is a common way for software to call functions over the web. Here, those functions run with APPS database privileges.

The second flaw, CVE-2026-114925, sits in the REST Services part of Oracle Applications Framework. A request handler there creates Java classes that the incoming request names. Horizon3 says it puts no limit on which classes may be named.

That hands the sender control over what code the server loads. Horizon3 describes this as a known weakness pattern that can turn a web call into code running on the application tier.

The two bugs cover for each other. The bypass removes the need for a password. The handler supplies the code. Horizon3 says the result is commands running under the same operating system account as the EBS application server.

What is known, and what is not

Oracle's advisory does not report exploitation in the wild. Neither CVE is in CISA's Known Exploited Vulnerabilities catalog. On November 18, CISA recorded an SSVC decision of "Exploitation: none" for both. SSVC is CISA's framework for triaging vulnerabilities.

That is reassuring, but it is a snapshot. Horizon3 reverse engineered Oracle's patch. So someone outside Oracle has already worked out what the fix changes. A patch can double as a description of the flaw. The report does not say anyone has attacked these flaws.

Why "not on the internet" is not enough

Horizon3 says internet exposure is not required. An attacker only needs to reach an EBS web address. That could be from an internal network, a partner network or a supplier network.

That list of networks is the real exposure map for an ERP system. In many organisations it is hard to answer quickly who is on it. Can your team write it down today?

The lesson here is that the trust boundary is every network that can reach the system. It is not the edge of the company.

The fix, and the limits of the stopgap

Oracle released its November 2026 Critical Security Patch Update on November 17. It fixes both CVEs. It covers supported releases 12.2.3 through 12.2.15. Oracle's advisory publishes no workaround for either flaw.

Until patching is possible, Horizon3 suggests limiting who can reach the EBS web and REST endpoints. Firewall rules or network segmentation can do that. Horizon3 is clear about the limit.

This step does not remove the flaw. It does not stop an attacker who already sits in a network segment that reaches EBS. Horizon3 calls it a workaround, not a fix.

There is one practical snag. Oracle gives no single fixed version number for these CVEs. Teams must look up the patch numbers in the E-Business Suite Patch Availability Document. Oracle's advisory links to it.

Questions for your team

Ask which of your E-Business Suite systems run 12.2.3 through 12.2.15. Ask whether the November 2026 update is installed on each. Ask for the list of networks, partners and suppliers that can reach those systems, and when it was last checked.

Ask whether anyone watches the application server account and the APPS database privileges for odd activity. If patching must wait for a maintenance window, ask who approves the delay. Ask what network limits apply in the meantime.

Once a patch ships, the flaw it fixes can be worked out from it, as Horizon3 showed. The question for the board is how long your ERP system sits between the two.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Horizon3.ai.