Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.
On November 17, 2026, Oracle released the Critical Security Patch Update addressing CVE-2026-114924 and CVE-2026-114925, two chained vulnerabilities rated CVSS 9.8 each that allow a remote, unauthenticated attacker to execute operating system commands on the Oracle E-Business Suite application tier via HTTP. The risk is not limited to internet-exposed systems: the chain works from any network segment that can reach the ERP's HTTP endpoints, including supplier and partner networks where segmentation is often weaker.
- CVE-2026-114924 is an authorization bypass in the Oracle Application Object Library Core; CVE-2026-114925 is an RCE in Oracle Applications Framework REST Services.
- Both carry CVSS v3.1 9.8 (Critical) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, per the official NVD record and Horizon3.ai analysis.
- Affected versions are Oracle E-Business Suite 12.2.3 through 12.2.15; patches are available in the November 2026 CSPU.
- Oracle reports no in-the-wild exploitation; CISA recorded SSVC "Exploitation: none" on November 18, 2026, and neither CVE appears in the KEV catalog.
The Mechanism: How the Shared Layer Becomes an Attack Amplifier
The chain triggers on the monolithic architecture typical of enterprise Oracle EBS deployments. CVE-2026-114924 resides in the Oracle Application Object Library Core, the shared layer that handles authorizations and sessions for the entire suite. An attacker sending specially crafted HTTP requests bypasses authorization checks and reaches protected REST functions with the privileges of the database APPS account.
From that position, CVE-2026-114925 takes over in the Oracle Applications Framework REST Services. The request handler instantiates Java classes whose names are supplied in the call input, without verifying which classes are permitted. This pattern turns a REST call into code execution on the application server, with the privileges of the account running EBS.
"Chained, they let a remote attacker with no credentials execute operating system commands on the EBS application tier over HTTP" — Horizon3.ai attack researchers
The chain is particularly insidious because it does not require internet exposure. According to Horizon3.ai, "any attacker who can reach an EBS HTTP endpoint from an internal, partner, or supplier network can attempt the chain." This mirrors a pattern already observed in enterprise architectures where EBS sits behind perimeter firewalls but remains accessible from third-party networks with which the organization shares procurement or supply-chain processes.
The Numerical Context: Where They Sit in the Oracle Attack Surface
The November 2026 CSPU includes, according to SecurityOnline, 71 entries in the EBS risk matrix. Of these, 19 are network-exploitable without credentials, and four reach the maximum CVSS 9.8 severity without requiring login: the two CVEs at the center of this article fall into that subset.
The official NVD record for CVE-2026-114924 shows a publication date of September 23, 2026, which is anomalous relative to the Oracle advisory timeline. It is unclear whether this date indicates prior responsible disclosure or a system error in the NVD database; the uncertainty does not alter the current vulnerability status but suggests caution when reconstructing the pre-patch timeline.
The CIS/MS-ISAC Advisory 2026-135 corroborates the RCE criticality in the November 2026 package, although the available text exhibits cookie-banner corruption and focuses more heavily on other vulnerabilities, leaving EBS with fewer specific details. The convergence among the primary technical source, the official CVE record, and the security advisory remains solid on the score and nature of the two flaws.
Recent History: Why EBS Is in Attackers' Crosshairs
Oracle E-Business Suite manages finance, human resources, procurement, and supply chain for large organizations. Compromise of the application tier exposes payroll, supplier data, customer data, and business-critical configuration parameters. The impact is not limited to confidentiality: command execution on the application server enables lateral movement to the database, alteration of approval workflows, or injection of fraudulent transactions.
The recent history of EBS in the CISA KEV catalog demonstrates that attackers target this platform. The chaining of an authentication bypass in a shared layer with an RCE in a REST service replicates a recurring architectural pattern: when the foundational component fails, it voids the security guarantees of every component that depends on it.
What to Do Now
The following actions derive directly from the documented facts:
- Apply the November 2026 CSPU patches for CVE-2026-114924 and CVE-2026-114925 on all Oracle EBS 12.2.3–12.2.15 instances, prioritizing systems with access from partner or supplier networks.
- Verify that EBS HTTP/REST endpoints are not reachable from network segments not explicitly required for business processes; the source identifies network access restriction as the only documented interim mitigation from Oracle.
- Review access logs for Oracle Applications Framework REST endpoints for anomalous requests containing Java class names prior to the patch date, with attention to origins from internal and third-party networks.
- Confirm that the CVSS 9.8 score and the remote, unauthenticated attack vector are correctly communicated to risk-management teams for patching priority assessment.
Editorial Close
CVE-2026-114924 and CVE-2026-114925 represent an architectural lesson: two separate flaws in distinct components become a systemic threat when chained. The absence of confirmed exploitation and the availability of a patch provide a window for action, but the unauthenticated nature of the chain and its operability from internal networks make every day of delay a calculated risk against financial and operational data.
Organizations running Oracle EBS must treat this CSPU as a priority not because of media pressure, but because of the simplicity of the attack vector and the completeness of the impact. The patch exists; the chain is documented; the attack surface includes networks that many security teams underestimate. The rest is execution.
Sources
Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.