Large Oracle E-Business Suite estates rarely fit a simple asset-owner model. Application teams, database administrators, network groups, and business units may each control part of the path affected by CVE-2026-114924. Closure requires evidence that those parts agree.

Vulnerability overview

Oracle published CVE-2026-114924 on November 17, 2026, in its November Critical Security Patch Update. The affected product is Oracle E-Business Suite, with Oracle Application Object Library Core identified as the vulnerable module and component.

Supported versions 12.2.3 through 12.2.15 are affected. Oracle assigns CVSS 3.1 a score of 9.8 and describes an unauthenticated network attacker using HTTP to take over the component. CISA ADP maps the defect to CWE-306. The reviewed record does not report confirmed exploitation.

Mechanism and exploitation conditions

The vendor identifies a missing authentication condition on a critical function but does not publish the code-level detail or request sequence.

The estate record should therefore capture evidence rather than assumptions: supported release, package state, application tier, HTTP route, trust zone, and business owner. A team that only records a scanner result has not shown that the vulnerable component is reachable. A team that only records a firewall rule has not shown that the application is patched.

This separation also makes review easier. Missing version evidence, missing patch evidence, and missing route evidence require different owners and different follow-up actions.

Impact

Oracle states that exploitation can result in takeover of Oracle Application Object Library. The business consequence depends on the workflows, integrations, and data available through that deployment.

Portfolio owners should use the vendor impact for prioritization and the application's own criticality for scheduling. They should not claim actual compromise unless an investigation supports it. A high CVSS score is a reason to act quickly, not a substitute for evidence.

Affected products and scope

The vendor range is EBS 12.2.3 through 12.2.15 for Application Object Library Core. Include all running instances, standby environments, shared integration platforms, and recently restored systems.

Record ownership at the level that controls the change. A central platform team may patch the technology stack while a business application team controls the release calendar and a network team controls public access. The closure record needs a named accountable owner across those boundaries.

Exposure context

The selected ZoomEye Search query app="Oracle E-Business Suite" returned 15,441 product-fingerprint matches. The CVE Filter vul.cve="CVE-2026-114924" returned 0. Exposure is 15,441.

This count is broad product exposure and does not prove vulnerable or compromised systems. Use it to test whether the owned inventory is missing internet-facing EBS products, then resolve each discovery through direct ownership and configuration checks.

Remediation and mitigations

Create a portfolio work item for every owned EBS deployment. Capture the current version, patch prerequisites, business change window, active HTTP paths, interim restrictions, and evidence source. Apply Oracle's November 2026 patch through the applicable availability document and verify the running application tier.

After patching, test the business interface and the trusted network paths. Confirm that temporary restrictions are either removed or retained with a valid decision. Review the exposure period for anomalous access, then record the investigation scope and confidence.

An item should remain open when any of these facts is unknown: owner, affected release, package state, active service, reachability, or validation result. This rule prevents a dashboard from showing completion based on an old inventory row.

Finally, feed the validated inventory back into the next patch cycle. Recheck internet exposure, because a route can change without a software release. The patch addresses the flaw; ownership and evidence keep the estate from drifting back into the same blind spot.

References