dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2026-46934

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Complex Maintenance, Repair and Overhaul product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Complex Maintenance, Repair and Overhaul. Successful attacks of this vulnerability can result in takeover of Oracle Complex Maintenance, Repair and Overhaul. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection or authentication bypass in Oracle E-Business Suite's Complex Maintenance, Repair and Overhaul Internal Operations component allows low-privileged remote attackers to execute arbitrary commands via crafted HTTP requests, leading to complete system compromise. The high attack complexity (AC:H) suggests the vulnerability requires specific conditions or expertise to exploit reliably.

MitigationApply Oracle Critical Patch Update when released; restrict HTTP/HTTPS access to the Internal Operations module to trusted IP ranges; monitor Oracle security alerts for patch availability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Complex Maintenance Repair And OverhaulApplication
Affected:>= 12.2.3, <= 12.2.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oracle E-Business Suite installation
    Run 'adident Header $APPL_TOP/admin/adinventory.xml' or query FND_PRODUCT_INSTALLATIONS table, or access Oracle Applications Manager (OAM) at /oamconsole
    Affected if Oracle E-Business Suite is not installed, then not affected
  2. Identify CMRO module version
    Query SELECT patch_level FROM fnd_product_installations WHERE application_id IN (SELECT application_id FROM fnd_application WHERE application_short_name = 'CSD'); or check the patch level file in $CSD_TOP/patch/115
    Affected if Version is between 12.2.3 and 12.2.15 inclusive, then potentially affected; outside this range means not affected
  3. Verify Complex Maintenance Repair and Overhaul module is enabled
    Query SELECT responsibility_name FROM fnd_responsibility WHERE responsibility_key LIKE '%CSD%' or check module status in Oracle Applications Manager under Module Quick Links
    Affected if Module is not enabled or not present, then not affected as the attack surface does not exist
  4. Check Internal Operations module accessibility
    Verify HTTP/HTTPS access to the Internal Operations component endpoint (typically under /OA_HTML/ or /csd/ namespace); confirm the web listener is exposed to network
    Affected if Module is accessible over network and not restricted to trusted IPs, then exposed to potential attack
  5. Review HTTP access logs for suspicious CMRO requests
    Examine Apache or Oracle HTTP Server access logs for the CMRO module endpoints for SQL injection patterns (UNION, SELECT, OR 1=1) or authentication bypass attempts; logs typically in $LOG_HOME/ora/10.1.3/Apache/access_log
    Affected if Evidence of targeted SQL injection or authentication bypass attempts found, then likely exploited

Affected if Oracle E-Business Suite with CMRO module version 12.2.3 through 12.2.15 is installed and the Complex Maintenance Repair and Overhaul Internal Operations component is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.15
Interim mitigation

Apply Oracle Critical Patch Update when released; restrict HTTP/HTTPS access to the Internal Operations module to trusted IP ranges; monitor Oracle security alerts for patch availability.

Recommended fix Moderate confidence

Contact Oracle for the fixed release; Oracle E-Business Suite patches are released via Critical Patch Updates (CPUs)

  1. Contact Oracle Support to obtain the specific patch for CVE-2026-46934
  2. Request the latest Oracle E-Business Suite Critical Patch Update (CPU) that addresses this vulnerability
  3. Apply the patch following Oracle's standard patching procedures for Oracle Complex Maintenance, Repair and Overhaul
  4. After patching, verify the fix by reviewing Oracle's patch documentation and testing the Internal Operations component
Caveat Review Oracle's patch notes for any post-patching requirements or additional steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46934 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data