If you run Oracle E-Business Suite 12.2.3 through 12.2.15, the November 2026 Critical Security Patch Update belongs on your application tier this week. Two of its fixes, CVE-2026-114924 and CVE-2026-114925, chain into remote code execution with no login, and a public analysis of how they combine went up on November 19.
Oracle shipped the patches on November 17 and scored each flaw 9.8 out of 10. Two days later, Horizon3.ai published its breakdown of the chain, which its researchers built by reverse engineering Oracle's fix. No one has reported exploitation so far, and neither CVE is in the US Cybersecurity and Infrastructure Security Agency (CISA) list of known exploited vulnerabilities. On EBS, that quiet period has not lasted long before.
What the two Oracle E-Business Suite flaws do together
CVE-2026-114924 sits in Oracle Application Object Library, the shared foundation under every EBS module, and Horizon3 classes it as an authorization bypass. CVE-2026-114925 is a remote code execution (RCE) bug in Oracle Applications Framework, filed by Oracle under its REST Services piece. Oracle's records for CVE-2026-114924 and CVE-2026-114925 describe both as reachable over HTTP by an attacker with no credentials, with low attack complexity and no user interaction.
According to Horizon3, the bypass opens protected REST functions that execute with the privileges of the APPS database account. The second bug sits in a request handler that builds Java objects from class names taken out of the request, with no list restricting which classes are allowed. Put together, an outsider ends up running operating system commands on the server that hosts the EBS web and application tier.
The exposure detail most teams will get wrong: Horizon3 says the chain does not need an internet-facing instance. If something on your network can reach the EBS web listener, it can attempt the chain. An ERP server labeled "internal only" is still in reach of every compromised laptop and vendor VPN account that can talk to it.
Am I affected? Check the EBS release level
Yes, if your instance runs any release from 12.2.3 to 12.2.15 without the November 2026 patches. Oracle lists that whole range as affected for both CVEs and does not name a fixed release number. The fix is a set of patches named in Oracle's EBS patch availability document, which sits behind a My Oracle Support login.
A database administrator can confirm the release by reading RELEASE_NAME from FND_PRODUCT_GROUPS. Oracle's advisory assesses supported releases only and does not say whether older 12.x installs are affected; we would treat any such install as potentially exposed, with no fix available through this update.
Two of four no-login 9.8 flaws in the same EBS advisory
The published research is about the chain. Oracle's EBS risk matrix for November lists four flaws scored 9.8 that need no credentials, and the two outside the chain get no less dangerous because nobody has written them up yet.
| CVE | EBS product | Component | Login needed |
|---|---|---|---|
| CVE-2026-114924 | Oracle Application Object Library | Core | No |
| CVE-2026-114925 | Oracle Applications Framework | REST Services | No |
| CVE-2026-114880 | Document Management and Collaboration | Attachments | No |
| CVE-2026-114863 | Oracle Universal Work Queue | Media Integration issues | No |
Across the whole update, Oracle counts 71 new EBS security patches, 19 of them remotely exploitable without authentication. Picking out the two patches tied to the published chain would leave 17 unauthenticated bugs in place. The only sensible scope is the full EBS set.
Why a published patch diff on EBS starts a countdown
E-Business Suite has a short and recent record here. In our June coverage of CVE-2026-46817, an Oracle Payments flaw went from Oracle's May patch to in-the-wild exploitation in roughly six weeks, with no public exploit code anywhere, which points to attackers rebuilding it from the fix. That followed the 2025 extortion campaign linked to the Cl0p group, which used CVE-2025-61882, another pre-authentication EBS bug, against EBS customers.
This time the reverse engineering took two days and was done in public by a research team. Horizon3's page does not say whether exploit code is available, and a GitHub search on November 20 turned up no repositories for either CVE. That buys some time. It does not change which direction the clock runs: every detail Horizon3 published is a detail an attacker no longer has to find alone.
EBS patching is slow for structural reasons. Heavy customization and online patching cycles push many shops to quarterly windows. For this update, the window is the wrong unit. We would treat the November EBS patches as an emergency change, the same way most teams already treat their edge VPN appliances.
Watching the application tier until the patches land
Neither Oracle nor Horizon3 has published indicators of compromise, so detection here means watching for the outcome rather than a signature. The useful signals are on the application tier itself: requests to EBS REST endpoints from addresses that never call them, and shell or download tools started by the operating system account that runs EBS.
T1190 Exploit Public-Facing Application Unauthenticated HTTP requests to EBS REST service endpoints from source addresses outside your user and integration ranges T1059.004 Command and Scripting Interpreter: Unix Shell sh or bash processes whose parent is an EBS WebLogic Java process, running as the EBS OS owner (commonly applmgr) T1105 Ingress Tool Transfer curl or wget started by the EBS OS owner, or new outbound connections from the application tier to the internet Published IOCs: none as of 2026-11-20 (Oracle and Horizon3 list none)
An EBS application tier has very little reason to spawn an interactive shell from its web-serving Java processes during business hours. If your endpoint or audit logging on those hosts can flag that parent and child pairing, it is the highest-value alert you can add before patching. If it already fired since November 17, treat the host as compromised rather than vulnerable.
Apply all 71 EBS patches, not only the chain's two
-
Patch the full November 2026 EBS set using Oracle's EBS patch availability document, on every 12.2.3 to 12.2.15 instance, starting with any that external users or partners can reach.
-
Narrow who can reach the EBS web and REST listeners down to the user VPN ranges and integration hosts that need them. Horizon3 calls this a workaround, not a fix, and it does nothing against an attacker already inside an allowed segment.
-
Add the parent and child process alert above on application tier hosts, and review web access logs back to November 17 for unauthenticated REST calls from unfamiliar sources.
-
Mark the date. Oracle's next Critical Security Patch Update is December 15, 2026, so plan for the EBS change process to run monthly, not quarterly.
If you track exposure across a fleet, continuous vulnerability detection is how an unpatched EBS host shows up before an attacker finds it. For more on Oracle's patch cycle and the products around EBS, see our write-up of the July 2026 WebLogic and Coherence fixes and the exploited WebLogic proxy flaw CVE-2026-21962.