Introduction
According to Oracle, a low-privileged account and HTTP access are enough for an attacker to take over Oracle Purchasing on Oracle E Business Suite (EBS) releases 12.2.3 through 12.2.15. Purchasing automates buying, manages the supplier base, and sits at the center of procurement workflows, so CVE-2026-83362 matters to any organization whose purchase orders and supplier data live in EBS.
Oracle fixed the issue in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026. Oracle, acting as the CVE Numbering Authority, rates it CVSS 3.1 8.8 (High). Some vulnerability feeds list the vendor as Unknown, but the affected vendor is Oracle Corporation.
Technical information
What Oracle has disclosed
The flaw is in the Internal Operations component of Oracle Purchasing. Oracle describes it as easily exploitable by a low-privileged attacker with network access via HTTP, and states that successful attacks can result in takeover of Oracle Purchasing. The published vector is:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Breaking the vector down:
- AV:N (Network): reachable over the network, and the description specifies HTTP.
- AC:L (Low complexity): no special conditions beyond access are described.
- PR:L (Low privileges): the attacker needs an authenticated, low-privileged session.
- UI:N (None): no victim interaction is required.
- S:U (Unchanged scope): impact is confined to the vulnerable component's security authority.
- C:H / I:H / A:H: high confidentiality, integrity, and availability impact.
The 8.8 score is Oracle's CNA assessment. NVD displays it but does not provide a separate NVD assessment, so it should not be described as an independently calculated NIST rating.
Root cause: what is and is not known
Oracle does not publish root-cause descriptions, CWEs, or code diffs for EBS fixes, and the NVD record lists no CWE. There is no public commit or code snippet showing what changed. The fix ships as a proprietary product update. VulDB titles its entry under privileges management, but that is VulDB's label, not a vendor-supplied weakness classification.
As a result:
- Classifying the bug as SQL injection, command injection, insecure deserialization, or any other specific weakness class is unsupported by the public record.
- The EBS responsibility, role, or permission an attacker needs is not disclosed.
- The vulnerable endpoint, request parameters, and request sequence are not disclosed.
- How the Internal Operations functionality leads to takeover is not explained.
The documented outcome is takeover of Oracle Purchasing. The public record does not establish operating system control, compromise of other EBS modules, or lateral movement, and we do not extend the impact beyond what Oracle states.
Attack flow based on public information
The disclosed preconditions allow only a high-level outline:
- The attacker obtains a low-privileged account on the target EBS instance (any account meeting the undisclosed privilege requirement).
- The attacker reaches the EBS application tier over HTTP.
- The attacker sends requests to the vulnerable Internal Operations functionality of Oracle Purchasing. No user interaction is needed, and attack complexity is low.
- Successful exploitation yields takeover of Oracle Purchasing, with high impact to confidentiality, integrity, and availability of that application.
Step 3 is where the public detail ends. Anyone presenting a specific endpoint or payload for this CVE is going beyond what Oracle, NVD, or the CVE record contain.
Reading the score in context
FIRST's CVSS v3.1 specification describes the base score as intrinsic severity, with temporal and environmental metrics for deployment context. An 8.8 base score therefore does not, by itself, establish exposure in a particular deployment or show exploitation in the wild. PR:L means this is an authenticated attack, but in EBS environments with many internal users, supplier-facing access, or shared accounts, a low-privilege requirement is not a strong barrier.
Exploitation status
Active exploitation is not publicly confirmed in the available evidence, and no threat actor is associated with this CVE. VulDB reports that no exploit is available, which reflects that source's assessment rather than proof that no private exploit exists. Rapid7's entry repeats the description and severity without an exploitation procedure. The available CISA KEV catalog content does not establish whether this CVE is listed. Unknown exploitation status is not the same as confirmed absence of exploitation.
Patch information
Oracle fixed CVE-2026-83362 in the November 2026 Critical Security Patch Update, released 17 November 2026 (advisory Rev 1, Initial Release). The CVE appears in the EBS risk matrix of that advisory, and the NVD record links to the same advisory as its only solution reference.
How the fix is distributed
- The advisory has no direct download link for an individual patch.
- For EBS, it points to the Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026), My Oracle Support Note KA923, which lists the patches each environment needs.
- KA923 sits behind a My Oracle Support sign-in, so specific patch numbers and prerequisite levels are available only to customers with valid support contracts. We could not view them publicly.
- The advisory lists CPU433 as its overall executive summary and analysis document.
- Release 12.2.15 is inside the affected range and must not be treated as a fixed version.
What else to patch alongside it
- Database and Fusion Middleware tiers: Oracle states that EBS exposure also depends on the Oracle Database and Oracle Fusion Middleware versions underneath it. Fixes for those components are not listed in the EBS risk matrix. Oracle recommends applying the November 2026 CSPU to those tiers too, so patching the Purchasing code alone does not fully meet Oracle's guidance.
- Skipped updates: Patches are provided only for versions under Premier or Extended Support. Customers who skipped earlier CPUs or CSPUs are told to review those advisories. Several earlier 2026 advisories (the August CSPU and October CPU) also fixed other Oracle Purchasing Internal Operations CVEs, so confirm that your EBS baseline is current.
- Out-of-band alerts: Oracle advises applying the fixes from its October 2026 Security Alerts (CVE-2026-91403, CVE-2026-114820, CVE-2026-109618/109619) together with this CSPU.
Interim measures from Oracle
Until patches are applied, Oracle's general advisory guidance is that blocking network protocols required by an attack, or removing unnecessary privileges or access to packages, may reduce risk. For this CVE, HTTP is the access protocol, but Oracle provides no endpoint-specific blocking rule and does not identify which privilege must be removed to neutralize the attack. Oracle warns that both approaches can break application functionality, recommends testing them in nonproduction systems, and states that neither is a long-term solution because neither corrects the underlying problem.
The only fix is Oracle's November 2026 CSPU for EBS. Obtain the patch set listed in MOS Note KA923 for your 12.2.x release and apply it together with the matching Database and Fusion Middleware CSPU patches.
Affected systems and versions
- Product: Oracle Purchasing, part of Oracle EBS
- Component: Internal Operations
- Affected supported versions: 12.2.3 through 12.2.15 (inclusive)
- Access requirement: network access via HTTP with a low-privileged account
- Related dependency: exposure of the overall EBS environment also depends on the underlying Oracle Database and Oracle Fusion Middleware versions, which Oracle patches separately
Oracle Fusion Cloud Procurement is a separate Oracle procurement platform. The vulnerability record identifies only Oracle Purchasing within EBS.
Vendor security history
EBS has a recent record of serious, actively exploited vulnerabilities, which is useful context for patch prioritization but not evidence about this CVE.
- CVE-2025-61882: Oracle issued a security alert on 4 October 2025 for an EBS vulnerability that was remotely exploitable without authentication and could result in remote code execution. The alert provided a patch and identified the October 2023 Critical Patch Update as a prerequisite. That prerequisite applies to CVE-2025-61882, not to CVE-2026-83362.
- CVE-2025-61884: Oracle issued an alert initially released on 11 October 2025 for an unauthenticated EBS vulnerability that could allow access to sensitive resources, with a base score of 7.5.
- 2025 extortion campaign: Google Threat Intelligence Group and Mandiant documented an EBS exploitation and extortion campaign associated with CVE-2025-61882, in which attackers in some cases exfiltrated significant amounts of data. GTIG did not formally attribute the activity to a tracked group and cautioned that the CL0P ransomware and data leak site are not used exclusively by FIN11.
- Earlier 2026 Purchasing fixes: The August 2026 CSPU and October 2026 CPU also addressed other Oracle Purchasing Internal Operations CVEs.
CVE-2025-61882 was unauthenticated, with a documented remote code execution outcome and observed data theft. CVE-2026-83362 requires low privileges and is documented as enabling takeover of Oracle Purchasing. Nothing in the record links the new flaw to the 2025 campaign or to any actor.
References
- NVD entry for CVE-2026-83362
- CVE Record: CVE-2026-83362
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- My Oracle Support Note KA923 (sign in required)
- Rapid7 Vulnerability Database entry for CVE-2026-83362
- VulDB entry 439029
- Oracle Security Alert for CVE-2025-61882
- Oracle Security Alert for CVE-2025-61884
- Google Threat Intelligence Group: Oracle EBS Zero Day Exploited in Widespread Extortion Campaign
- Oracle E Business Suite Applications overview
- Oracle E Business Suite documentation
- Oracle Named a Leader in 2025 Gartner Magic Quadrant for Source to Pay Suites
- CISA Known Exploited Vulnerabilities Catalog
- FIRST CVSS v3.1 Specification Document



