Enterprise Command Center FrameworkApplication · Oracle

CVE-2026-46900

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Enterprise Command Center Framework product of Oracle E-Business Suite (component: Core). Supported versions that are affected are V15 and V16. Easily exploitable vulnerability allows low privileged attacker with network access via HTTPS to compromise Oracle Enterprise Command Center Framework. While the vulnerability is in Oracle Enterprise Command Center Framework, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Enterprise Command Center Framework. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 · high confidence

Critical remote code execution vulnerability in Oracle Enterprise Command Center Framework core component allowing low-privileged remote attackers to completely take over the system via HTTPS. The scope change indicates attacks may propagate to additional Oracle products. CVSS 9.9 reflects complete confidentiality, integrity, and availability compromise with no user interaction required.

MitigationApply Oracle Critical Patch Updates (CPU) for Oracle E-Business Suite addressing the Enterprise Command Center Framework vulnerability in versions 15 and 16. Until patched, restrict network access to ECCF HTTPS endpoints and monitor for indicators of compromise.

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
Enterprise Command Center FrameworkApplication
Affected:= 15= 16

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify if Oracle Enterprise Command Center Framework is installed
    Check your Oracle E-Business Suite installation for the presence of the Enterprise Command Center Framework component. This is typically found in the Oracle ApplicationsManager or through Oracle Applications DBA (AD) utilities.
    Affected if The component is present in the Oracle E-Business Suite installation
  2. Determine the installed ECCF version
    Query the Oracle database or use Oracle Application Manager to retrieve the Enterprise Command Center Framework version number. Look for version 15 or version 16 specifically.
    Affected if The installed version is 15 or 16
  3. Verify if HTTPS endpoints for ECCF are accessible
    Check network configuration and determine if ECCF HTTPS endpoints are exposed to the network. Review web server configuration for Oracle Enterprise Command Center Framework virtual paths.
    Affected if ECCF HTTPS endpoints are externally accessible or accessible beyond the trusted network
  4. Confirm if the core ECCF component is enabled
    Review the Oracle E-Business Suite configuration to determine if the Enterprise Command Center Framework core component is enabled and running.
    Affected if The core ECCF component is enabled and processing requests

If Oracle Enterprise Command Center Framework versions 15 or 16 are installed with the core component enabled and HTTPS endpoints accessible, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates (CPU) for Oracle E-Business Suite addressing the Enterprise Command Center Framework vulnerability in versions 15 and 16. Until patched, restrict network access to ECCF HTTPS endpoints and monitor for indicators of compromise.

Fix this in Enterprise Command Center Framework Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-46900 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