Introduction
Oracle's November 2026 Critical Security Patch Update fixes a flaw that lets an unauthenticated attacker with HTTP access to the Admin UI of Oracle Mobile Field Service obtain unauthorized access to critical data, or complete access to all data the application can reach. Mobile Field Service holds the customer, contact, installed base and entitlement details that field technicians work from, so a confidentiality flaw here translates directly into exposure of service operations data.
Oracle Mobile Field Service is a module of Oracle E Business Suite (EBS) that gives technicians access to tasks, service requests, parts ordering and receipt, and a knowledge repository. Oracle places it within the EBS Field Service suite alongside Teleservice, Field Service, Advanced Scheduler and Spares Management. It ships as part of Oracle's enterprise applications portfolio rather than as a standalone product, so its exposure follows EBS deployments. The sources we reviewed do not provide an independent market share figure for Mobile Field Service itself.
Technical information
What the records confirm
CVE-2026-114885 was published on 17 November 2026 with Oracle as the CNA. NVD reproduces Oracle's assessment and has not supplied its own. Oracle's risk matrix lists the issue in its own row: Oracle Mobile Field Service, component Admin UI, protocol HTTP, Remote Exploit without Auth: Yes, CVSS 3.1 base score 7.5.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- AV:N: reachable over the network (HTTP)
- AC:L: low attack complexity
- PR:N: no privileges or authentication required
- UI:N: no user interaction
- S:U: scope unchanged
- C:H / I:N / A:N: high confidentiality impact, with no integrity or availability impact scored
Root cause
Oracle EBS is closed source, and Oracle has not published a code change, diff or changelog for this fix. The NVD weakness section contains no CWE assignment. VulDB classifies the issue as CWE-285, Improper Authorization, but also describes the affected code block and input as unknown, so that label is a secondary classification rather than a root cause confirmed by Oracle.
The public record does establish the shape of the failure: an unauthenticated HTTP request to the Admin UI component can result in access to data that Mobile Field Service should protect. Despite the component name, Admin UI does not require administrator credentials. The vector explicitly sets PR:N.
Attack flow
Based only on the disclosed information, exploitation looks like this:
- The attacker identifies an Oracle EBS instance running Mobile Field Service in the 12.2.3 through 12.2.15 range whose Admin UI is reachable over HTTP.
- The attacker sends HTTP requests to the Admin UI component without any credentials.
- No victim interaction and no special conditions are required (UI:N, AC:L).
- The result is unauthorized access to critical data, or complete access to all data accessible to Oracle Mobile Field Service.
No request path, HTTP method, parameter, payload, vulnerable function or reproducible exploit sequence has been published, and we are not going to guess at one.
Impact boundaries
The documented consequence is data exposure. The record does not describe remote code execution, modification of business records or service disruption, and the unchanged scope means the stated impact concerns data accessible to Mobile Field Service, not every EBS module. Oracle documents that Mobile Field Service gives technicians customer, contact, installed base and entitlement details. That describes what the product handles. It does not confirm that any specific customer's records have been exposed.
Exploitation status
In the sources reviewed (dated 18 November 2026), active exploitation is not established, no threat actor is attributed, and VulDB reports no public exploit or technical details. The exact CVE was not visible on the reviewed CISA KEV catalog page. These gaps reflect the limits of public evidence and do not prove that attacks cannot occur. The access conditions remain permissive regardless.
Patch information
Oracle fixed CVE-2026-114885 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026, for supported releases 12.2.3 through 12.2.15.
What Oracle published
- Advisory listing: The November 2026 CSPU risk matrix includes a dedicated row for CVE-2026-114885 (Mobile Field Service / Admin UI, HTTP, remote exploit without auth, CVSS 7.5, confidentiality only).
- Internal tracking ID: Oracle's machine-readable CSAF advisory links the CVE to Oracle Bug ID 39390597 for Oracle Mobile Field Service. Individual EBS fixes are usually listed by bug number, not CVE, so this is the number to look for in patch READMEs and when working with Oracle Support.
- Remediation type: The CSAF record marks the remediation as
vendor_fixwith the note "Oracle customers with valid support contracts". The fix is available through My Oracle Support (MOS), not as a public download.
How the fix is delivered
EBS security fixes ship as a set of EBS CSPU patches rather than a single product upgrade. Oracle documents two entry points:
- MOS Article KA923, the document for identifying the latest monthly and quarterly Critical Patch Update for Oracle EBS Release 12.2. Both the advisory and the CSAF remediation URL point here. It always links to the current EBS CPU and CSPU documentation.
- MOS Article KA1855, the Oracle EBS Release 12.2 Critical Security Patch Update Availability Document (November 2026). Oracle's EBS Technology blog names this as the document listing the actual patch numbers to apply.
Database and middleware layers
Oracle's EBS notes state that EBS runs on Oracle Database and Oracle Fusion Middleware components, and that fixes for those layers are not included in the EBS risk matrix. Oracle recommends applying the November 2026 CSPU to the database and middleware components of an EBS installation as well as the application-tier fix for Mobile Field Service.
Verifying the fix
Oracle has updated the EBS Critical Patch Update Checker (ECPUC), delivered as Patch 35583866, with the November 2026 CSPU content:
- The patch includes the script
ECPUC.sql, which writes a report,ECPUC.lst, showing the current EBS CSPU/CPU level and the required patches and security fixes still missing. - Oracle recommends running ECPUC before patching to see what is needed, and again after applying patches and completing the online patching cutover to confirm everything was applied.
- Use the latest ECPUC version. Older copies do not know about newer CSPU fixes and would not flag a missing fix for bug 39390597.
Interim risk reduction
Oracle's general advisory guidance notes that blocking network protocols required by an attack may reduce risk while patches are pending. For this CVE, that protocol is HTTP. Oracle publishes no CVE-specific filtering rule, warns that protocol restrictions may break application functionality, recommends testing outside production, and states that such measures are not long-term solutions. Oracle's generic advice about removing unnecessary privileges applies to attacks that require privileges, which this one does not.
Affected systems and versions
- Vendor: Oracle Corporation
- Product: Oracle Mobile Field Service, part of Oracle EBS
- Component: Admin UI
- Affected supported versions: 12.2.3 through 12.2.15
- Exposure condition: Admin UI reachable by an attacker over HTTP, with no authentication required
Oracle provides CSPU patches only for releases under Premier Support or Extended Support. Unsupported releases are not tested for the vulnerabilities addressed by the update, so a release falling outside the listed range should not be read as confirmation that it is safe. Nor does the affected range ending at 12.2.15 mean that a particular later release contains the fix. Use KA923, KA1855 and ECPUC to determine the state of a given environment.
Vendor security history
Oracle's security fixing policy describes quarterly Critical Patch Updates, smaller targeted Critical Security Patch Updates for high-priority issues between quarterly releases, and the option to issue patches or workaround instructions out of schedule for particularly critical vulnerabilities or reported active exploitation. Oracle's November 2026 advisory also notes that attackers have succeeded against some customers because available patches had not been applied.
A concrete EBS precedent is CVE-2025-61882, a separate vulnerability. On 6 October 2025 the UK NCSC reported active exploitation of that unauthenticated EBS flaw, which could allow remote code execution and full system compromise without user interaction. Google's threat intelligence reporting described significant data exfiltration at some affected organizations, identified Oracle's emergency patches of 4 October 2025 as the critical step to prevent initial access, and noted overlaps with confirmed and suspected FIN11 activity while stating that GTIG had not formally attributed the activity to a tracked group.
That history shows the operational consequences of EBS compromise and Oracle's ability to ship emergency fixes. It does not indicate exploitation of CVE-2026-114885, and the two issues have different documented impacts: full system compromise in the earlier case, confidentiality only here.
References
- NVD: CVE-2026-114885
- CVE Record: CVE-2026-114885
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- Oracle CSPU November 2026 CSAF advisory (JSON)
- Oracle EBS Technology blog: Critical Security Patch Update for November 2026 now available
- Oracle EBS Technology blog: November 2026 updates to the EBS Critical Patch Update Checker (ECPUC)
- Oracle Security Fixing Policies
- Oracle Mobile Field Service data sheet
- Oracle Mobile Field Service Implementation Guide
- VulDB entry for CVE-2026-114885
- CISA Known Exploited Vulnerabilities Catalog
- About Oracle: Company Information
- Google Cloud: Oracle EBS zero day exploited in widespread extortion campaign
- UK NCSC: Active exploitation of vulnerability affecting Oracle EBS



