What happened
In November 2026, Oracle published a security bulletin that, among other things, fixes two critical vulnerabilities in Oracle E-Business Suite (EBS). EBS is a large enterprise resource planning (ERP) system used for accounting, purchasing, inventory, field service and HR. Both flaws were added to the US National Vulnerability Database (NVD) on November 17, 2026.
The first, CVE-2026-101691, sits in Oracle Mobile Field Service, specifically in its administration interface (Admin UI). The second, CVE-2026-114881, is in Document Management and Collaboration, in the part that handles file attachments (Attachments). Both affect versions 12.2.3 to 12.2.15.
At the time of writing, neither flaw appears in the CISA KEV catalog of actively exploited vulnerabilities, and the European EUVD database run by ENISA does not report exploitation either. So there are no publicly confirmed attacks yet. That can change quickly, so don’t put the update off.
Why it is dangerous
Both flaws share the worst possible trait: the attacker does not need to log in. All they need is network access to the system over HTTP, the same way an ordinary web browser connects. Oracle describes them as easily exploitable but has not published the exact type of programming error.
Picture an office building where every door needs a key card, except one side door to the archive that opens for anyone. Nobody has to break anything or know a password. That is what an unauthenticated vulnerability means.
For CVE-2026-101691, Oracle says an attacker can gain access to critical data or to all data Mobile Field Service can reach, and can also modify, insert or delete some of it. The flaw also involves a so-called scope change: the attack may significantly impact other products too. CVE-2026-114881 can lead to leakage of critical data and a complete outage of Document Management and Collaboration (hangs or repeated crashes).
Oracle’s descriptions do not mention full server takeover or spreading further across the network. Still, a data leak from an ERP system holding invoices, contracts and customer or employee records is a serious incident in its own right.
- CVSS is a severity scale from 0 to 10. Using CVSS 3.1, Oracle scored CVE-2026-101691 at 9.3 and CVE-2026-114881 at 9.1. Both fall in the “critical” band.
- CISA KEV is the US agency CISA’s list of vulnerabilities with confirmed exploitation. These two are not on it yet.
- EPSS estimates the likelihood of exploitation in the next 30 days. As of November 18, 2026, it is 0.51% for CVE-2026-114881 and 0.35% for CVE-2026-101691. Low values are typical for freshly disclosed flaws and can rise.
Who is affected
This affects organisations running Oracle E-Business Suite versions 12.2.3 to 12.2.15 with the Mobile Field Service or Document Management and Collaboration modules. EBS typically runs on in-house servers, in Oracle’s cloud or with a managed service provider. In Slovakia and the Czech Republic it is mostly found in larger companies, manufacturing, distribution, subsidiaries of multinational groups and some public institutions.
The highest risk is for installations whose web interface is reachable from the internet, for example for field technicians or suppliers. If EBS is only reachable from the internal network, the threat is an attacker who has already got inside.
Organisations that don’t use EBS are not affected by these two flaws. Oracle lists only the supported versions 12.2.3 to 12.2.15 as affected. It says nothing about older unsupported releases, so don’t assume they are safe.
How to check if you are affected
You can find the EBS version with a database query run as an account that can read the APPS schema. The query only reads data and changes nothing.
SELECT release_name FROM apps.fnd_product_groups;
A result between 12.2.3 and 12.2.15 means you are in the affected range. The next query shows whether the affected modules are installed. Status I means installed, S shared and N not installed.
SELECT a.application_short_name, a.application_name, p.status
FROM apps.fnd_application_vl a
JOIN apps.fnd_product_installations p ON p.application_id = a.application_id
WHERE a.application_name LIKE '%Field Service%'
OR a.application_name LIKE '%Document%';
This query lists the most recently applied patches. Compare the numbers with Oracle’s November 2026 bulletin.
SELECT * FROM (SELECT patch_name, creation_date FROM apps.ad_applied_patches ORDER BY creation_date DESC) WHERE ROWNUM <= 20;
Also check whether EBS is reachable from the internet by reviewing firewall, reverse proxy or load balancer rules. If a supplier manages your EBS, ask them in writing for the version and the list of applied patches.
How to fix it
Oracle released fixes in its November 2026 security bulletin at https://www.oracle.com/security-alerts/cspunov2026.html. The bulletin and the linked documents on My Oracle Support list the exact patch numbers for each 12.2.x release and their prerequisites. The NVD records do not mention a temporary workaround from the vendor.
- Identify your EBS version and installed modules (see the previous section).
- Find the patches for your release in the bulletin and on My Oracle Support, and check prerequisites such as the required AD and TXK levels.
- Back up both the application tier and the database, and apply the patch in a test environment first.
- Apply it to production with the
adoponline patching tool during a planned maintenance window. - Afterwards, confirm the patch is recorded in
ad_applied_patchesand test key business processes.
Work in this order: internet-facing instances first, then internal ones. Until you patch, we recommend as a general measure (not vendor guidance) restricting internet access to EBS, for example VPN only or an allowlist of IP addresses on the reverse proxy. The flaws are not in the CISA KEV catalog, so no binding CISA deadline applies, but the critical scores argue for a quick update.
What if you may already be compromised
Neither Oracle nor other sources have published specific indicators of compromise so far. If your EBS was reachable from the internet, at least check the following:
- Oracle HTTP Server access logs: unusual requests from unknown IP addresses, especially to the Mobile Field Service admin interface and attachment functions, and unusually large data downloads.
- Unexpected changes, inserted or deleted records in Mobile Field Service data.
- Hangs or repeated crashes of Document Management and Collaboration.
- New or unknown EBS user accounts, which this query lists:
SELECT user_name, creation_date, last_logon_date FROM apps.fnd_user WHERE creation_date > SYSDATE - 60 ORDER BY creation_date DESC;
If you find anything suspicious, don’t delete logs or restart the system without preserving its state, so it can be investigated. Bring in an incident response specialist. If personal data may have leaked, assess within 72 hours whether to notify your data protection authority under GDPR.