Introduction
A flaw fixed in Oracle's November 2026 Critical Security Patch Update allows anyone holding a low-privileged Oracle E Business Suite account to read, create, modify or delete the data that Oracle Mobile Field Service can reach, using only HTTP access and no victim interaction. Oracle scored CVE-2026-101652 at CVSS 3.1 8.1 (High). Mobile Field Service sits on the customer, product and service request records that field operations run on, so the integrity side of this bug matters as much as the disclosure side.
Oracle Mobile Field Service is a product within Oracle E Business Suite (EBS) that lets field technicians access customer, product and service request information, manage their schedules, order spare parts, and record materials, costs and labor. Oracle describes EBS as a longstanding enterprise applications portfolio used by thousands of organizations worldwide for core business operations, spanning financial, order management and service functions. That broad footprint, combined with recent large-scale attacks against EBS, is why even an authenticated data access flaw in one EBS product deserves attention from defenders.
Technical information
What Oracle has confirmed
Oracle, acting as the CNA, and NVD agree on the core facts. The vulnerability is in the Internal Operations component of Oracle Mobile Field Service, affects supported versions 12.2.3 through 12.2.15, and is described as easily exploitable by a low-privileged attacker with network access via HTTP. Oracle's EBS risk matrix marks the issue as not remotely exploitable without authentication.
The published vector is:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Decoded using FIRST's CVSS 3.1 definitions:
- AV:N (Attack Vector: Network): reachable over the network; Oracle specifies HTTP.
- AC:L (Attack Complexity: Low): no special conditions beyond the prerequisites.
- PR:L (Privileges Required: Low): the attacker needs a low-privileged account.
- UI:N (User Interaction: None): no victim needs to click or act.
- S:U (Scope: Unchanged): impact stays within the vulnerable component's authority.
- C:H (Confidentiality: High): access to critical data or to all data Mobile Field Service can access.
- I:H (Integrity: High): unauthorized creation, deletion or modification of that data.
- A:N (Availability: None): no availability impact is assigned.
PR:L and UI:N are separate properties. A victim does not have to do anything, but the attacker still needs valid low-privileged access. That requirement is what separates this issue from the unauthenticated EBS flaws that drove incidents in 2025.
Root cause: what is and is not known
EBS is closed source, and Oracle has published no diff, commit or code-level description of the fix. The public record does not identify an affected URL, parameter, vulnerable function, payload or request sequence. The NVD record contains no populated CWE entry.
VulDB, a third-party source, classifies the issue as improper authorization and associates it with CWE-285 and CWE-266. That classification fits the shape of the CVSS vector (a low-privileged user reaching data well beyond what that role should touch). It is not a confirmed assignment from Oracle or NVD, though, so we treat it as a plausible hypothesis rather than an established root cause. VulDB also labels the issue "critical" and mentions availability impact. Oracle's primary assessment is High with A:N, and we follow the primary source.
The public record contains no evidence of remote code execution, operating system takeover or SQL injection. Claims beyond a high-impact application data flaw would exceed the published evidence.
Attack flow based on published conditions
Without a disclosed endpoint or payload, the attack flow can only be described at the level the advisory supports:
- Prerequisite: the attacker holds a low-privileged account on the target EBS instance (PR:L).
- Reachability: the attacker can reach the EBS application tier over HTTP (AV:N).
- Exploitation: the attacker sends HTTP requests that reach the Mobile Field Service Internal Operations component. Oracle rates this as low complexity, and no other user needs to be involved (AC:L, UI:N).
- Outcome: the attacker gains read access to critical data or to all data Mobile Field Service can access, and can create, delete or modify it (C:H, I:H). Service availability is not affected (A:N).
Mobile Field Service handles customer details, service requests, schedules, parts orders, and labor and cost records. The integrity impact therefore means an attacker could tamper with operational and billing-relevant records as well as view them. The advisory does not tell us which specific records are reachable in a given deployment.
Exploitation status
- In the wild: not established by the NVD or CVE records reviewed as of 17 November 2026. The correct status is unconfirmed, which is not the same as "never exploited."
- Public exploit: VulDB reports that technical details are unknown and no exploit is publicly available. That does not rule out private exploits.
- CISA KEV: the retrieved CISA catalog search returned no entry for this identifier.
- Attribution: no threat actor or campaign is tied to this CVE. Actors linked to earlier EBS incidents should not be assumed to be involved.
As FIRST's specification notes, the 8.1 Base score reflects intrinsic characteristics of the flaw, not an observation of exploitation.
Patch information
Oracle fixed CVE-2026-101652 in its November 2026 Critical Security Patch Update (CSPU). The advisory's first revision ("Rev 1. Initial Release") was published on 17 November 2026. The CVE record Oracle published as CNA lists this CSPU advisory as its only vendor reference, so the CSPU is the official fix.
What the fix covers
The EBS risk matrix in the CSPU lists the following entry:
- CVE: CVE-2026-101652
- Product: Oracle Mobile Field Service
- Component: Internal Operations
- Protocol: HTTP
- Remote without auth: No
- CVSS 3.1: 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N)
- Affected versions: 12.2.3 through 12.2.15
The EBS section of the CSPU contains 71 new security patches, including the fix for this flaw. The "Remote without auth = No" designation is consistent with the vector, since exploitation needs a low-privileged EBS account. That shapes prioritization, but the patch should still be applied, because a successful attack grants full read and write access to Mobile Field Service data.
How to get the fix
The fix ships as binary EBS patches through My Oracle Support (MOS), which requires a support contract. Oracle does not name an individual patch number in the public advisory. Instead it directs EBS customers to a single knowledge document, the Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026), My Oracle Support Note KA923.
KA923 maps each EBS code level (12.2.3 through 12.2.15) to the patches it needs. Administrators should start there rather than looking for a standalone Mobile Field Service patch. The fix is not a version upgrade. Because the affected range runs up to 12.2.15, the remedy is to apply the November 2026 CSPU patches to your current 12.2.x code level.
Patch the underlying tech stack as well
Oracle points out that EBS includes Oracle Database and Oracle Fusion Middleware components, whose vulnerabilities are listed in their own risk matrices rather than the EBS one. Oracle therefore recommends applying the November 2026 CSPU to the Database and Fusion Middleware tiers of an EBS deployment too. Patching only the EBS application tier closes CVE-2026-101652 but may leave related exposure in the stack underneath.
Interim risk reduction
Oracle's general advisory guidance, which is not a CVE-specific workaround, notes that until patches are applied, risk may be reduced by:
- Blocking network protocols required by an attack (Oracle publishes no CVE-specific filtering rule).
- Removing privileges or package access from users who do not need them, where those are attack prerequisites (no specific role, privilege or package is named for this CVE).
Oracle cautions that these changes should be tested on nonproduction systems because they may break application functionality, and that neither change corrects the underlying vulnerability nor serves as a long-term solution.
What remains unconfirmed
Public sources do not give the specific MOS patch numbers, the code that changed in the Internal Operations component, or the confirmed root cause class. Any further detail is only available inside KA923 and the patch readmes on My Oracle Support.
Affected systems and versions
- Product: Oracle Mobile Field Service, part of Oracle E Business Suite
- Component: Internal Operations
- Affected supported versions: 12.2.3 through 12.2.15 (inclusive)
- Vulnerable configuration: any deployment in that range where an attacker holds a low-privileged account and can reach the application over HTTP
- Fixed by: November 2026 CSPU patches applied to the existing 12.2.x code level, per My Oracle Support Note KA923
Oracle states that unsupported releases are not tested for the vulnerabilities addressed in a patch update and recommends upgrading to supported versions. An installation outside the listed range should therefore not be assumed safe simply because it is not listed.
Vendor security history
Oracle documents formal Secure Coding Standards covering design principles, communications security, common vulnerabilities, data validation and user management, assessed throughout the supported product lifecycle, along with required security training for technical development staff. Fixes are delivered through quarterly Critical Patch Updates, targeted Critical Security Patch Updates such as the one covering this CVE, and Security Alerts for issues too critical to wait. Oracle does not distribute exploit or proof-of-concept code, which explains why advisories like this one describe impact without a reproducible attack.
EBS has drawn serious attention recently. In October 2025, Oracle issued a Security Alert for CVE-2025-61882, a flaw in Oracle Concurrent Processing, BI Publisher Integration that was remotely exploitable without authentication, could result in remote code execution, and was scored 9.8. Oracle published observed indicators of compromise alongside the fix.
Separately, Google Threat Intelligence Group and Mandiant documented a 2025 EBS extortion campaign by an actor claiming affiliation with the CL0P brand, including significant data exfiltration in some cases and extortion claims backed by legitimate file listings. Google reported overlap with FIN11-associated activity but did not formally attribute the campaign, noting that CL0P is not used exclusively by FIN11.
These cases show that EBS is an established target, but they differ from CVE-2026-101652 in important ways. The earlier flaw was unauthenticated with code execution impact, while this one requires low privileges and carries confidentiality and integrity impacts only. Neither the mechanism nor the actors from 2025 should be projected onto this CVE.
References
- NVD: CVE-2026-101652
- CVE Record: CVE-2026-101652
- CVE Services API record for CVE-2026-101652
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- Oracle Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins
- Oracle Critical Patch Update Advisory, October 2026
- VulDB: CVE-2026-101652 Oracle Mobile Field Service Internal Operations improper authorization
- CISA Known Exploited Vulnerabilities Catalog search
- FIRST CVSS v3.1 Specification Document
- Oracle Security Alert: CVE-2025-61882
- Google Cloud Blog: Oracle E Business Suite Zero Day Exploited in Widespread Extortion Campaign
- Oracle E Business Suite Applications
- Oracle Secure Coding Standards
- Oracle Field Service User Guide



