On this page (7 sections)
CVE-2026-114924 is a critical vulnerability in the Oracle Application Object Library (AOL) product of Oracle E-Business Suite, in the Core component. According to the NVD record, an unauthenticated attacker with network access via HTTP can compromise the component, and a successful attack can result in takeover of Oracle Application Object Library.
If your organization runs Oracle E-Business Suite 12.2 and any part of it is reachable via HTTP from a network you do not fully control, this deserves prompt attention. The public information is still thin, so this article separates what is confirmed from what you will need to verify in Oracle's own advisory.
What the record says
The NVD entry, published on 2026-11-17, describes an easily exploitable flaw in the Core component of Oracle Application Object Library. The affected supported versions are 12.2.3 through 12.2.15. The description says the attacker needs only network access via HTTP and no credentials.
The CVSS 3.1 vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, which produces a 9.8 base score. In plain terms: reachable over the network, low attack complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability.
- CVSS 3.1 base score (NVD record)
- 9.8
- Affected supported versions
- 12.2.3-12.2.15
- NVD publication date
- 2026-11-17
What we do not know yet
The NVD text is the only detailed source in our research, and only one independent publisher covers the story so far. Several things are not stated there, and you should not assume them either way:
- The specific weakness type (no CWE is listed) and the exact mechanism of the flaw.
- Which fixed version or patch level resolves it. The record points to Oracle's security alert page as its reference.
- Whether anyone is exploiting it. The research shows no CISA KEV listing and no reports of attacks, which is absence of evidence rather than proof of safety.
- Whether any workaround or mitigation exists short of patching.
Why a 9.8 with no login matters
The score reflects the conditions in the vector: no account, no user interaction, low complexity and high impact on confidentiality, integrity and availability. The record describes the outcome as takeover of Oracle Application Object Library. A flaw that needs no credentials removes the usual barriers such as stolen passwords or phishing, which is why such issues are normally treated as urgent.
Exposure is the key question for your own environment. An instance that can be reached via HTTP from the internet is the highest priority. Internal-only instances are still worth patching, since the record only requires network access, and any attacker who gains a foothold on your network may be able to reach them.
How to check whether you are exposed
First, confirm whether you run an affected release. Ask your Oracle DBA or EBS administrator to confirm the release level using Oracle's documented method for your installation, then compare it with the affected range of 12.2.3 through 12.2.15 and with the details in Oracle's security alert.
Then work out which HTTP endpoints of the suite are reachable and from where. Ask your network team for the external and internal listeners that front the EBS web tier, and compare that list with what you expect to be reachable. Include test, development and disaster recovery copies in the review.
What to do now
- Inventory every Oracle E-Business Suite instance, including test, development and disaster recovery copies, and record their release levels.
- Open Oracle's security alert for this CVE and identify the patch or fixed release that applies to your version.
- Schedule the patch with priority for internet-facing instances, then internal ones.
- Until patched, restrict HTTP access to the EBS web tier to known networks, VPN users or a reverse proxy with allow-listing where your architecture permits.
- Review web server and application logs since 2026-11-17 for unusual requests from unfamiliar addresses, and keep the logs for later investigation.
- Confirm backups are recent, stored separately and restorable before you change production.
- If you find signs of compromise, treat it as an incident: isolate the host, preserve evidence and rotate credentials and secrets used by the suite.
Detection and monitoring afterwards
Because the flaw is unauthenticated, logs from the web tier are a useful early signal. Watch for spikes of requests from single addresses, requests to unusual paths, unexpected errors and new or changed files on application servers. Alert on new administrative accounts or changes to application users in the suite.
From the outside, you can keep an eye on the things that change on a public-facing system. Webforta Monitor tracks uptime, certificate, DNS and header changes for sites you own, and the free SSL checker lets you confirm what certificate your public EBS hostname presents. These do not detect this vulnerability, and they are no substitute for patching. For broader background, see our guide to small business website security.
Timeline
| Date | Event |
|---|---|
| 2026-11-17 | CVE-2026-114924 published in NVD, referencing Oracle's security alert |
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.
