Enterprise Command Center FrameworkApplication · Oracle

CVE-2026-46897

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 HTTP 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 unauthorized creation, deletion or modification access to critical data or all Oracle Enterprise Command Center Framework accessible data as well as unauthorized access to critical data or complete access to all Oracle Enterprise Command Center Framework accessible data and unauthorized ability to cause a partial denial of service (partial DOS) 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:L).

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 vulnerability in Oracle Enterprise Command Center Framework (versions V15 and V16) allows low-privileged attackers with network access via HTTP to create, delete, or modify critical data, as well as gain unauthorized complete access to all accessible data. The scope change (S:C) indicates attacks can significantly impact additional Oracle products beyond the directly affected component.

MitigationApply the Oracle Critical Patch Update addressing this vulnerability for Oracle E-Business Suite; until patch is available, restrict network access to Enterprise Command Center Framework HTTP interfaces using network segmentation and authentication controls.

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
Low

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

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 for Oracle E-Business Suite installations and look for Enterprise Command Center Framework components in the Oracle application directory structure or Oracle Application Manager
    Affected if The product is present in the environment
  2. Determine the installed version of Enterprise Command Center Framework
    Use Oracle Application Manager or query the Oracle database for the ECCF version information typically stored in Oracle tables or Oracle Fusion Middleware inventory
    Affected if The version is 15 or 16 exactly as listed in affected versions
  3. Verify if HTTP interface for Enterprise Command Center Framework is enabled
    Check Oracle WebLogic Server or Oracle HTTP Server configuration for Enterprise Command Center Framework application endpoints, typically accessible via /ecc or similar ECCF-related URL paths
    Affected if HTTP endpoints for Enterprise Command Center Framework are exposed and accessible
  4. Assess network accessibility of ECCF HTTP interfaces
    Review network firewall rules, load balancer configurations, and web server access controls to determine if ECCF HTTP ports (commonly 8000-9000 range or standard Oracle WebLogic ports) are reachable from untrusted networks
    Affected if The HTTP interface is reachable from networks outside the trusted internal network
  5. Check for existing authentication controls on ECCF endpoints
    Review Oracle WebGate, Oracle Access Manager, or other authentication configurations protecting the Enterprise Command Center Framework application URLs
    Affected if No strong authentication or Oracle Access Manager protection is configured, allowing anonymous or low-privileged access

Environment is affected if Oracle Enterprise Command Center Framework versions 15 or 16 are installed and their HTTP interfaces are network-accessible without adequate access controls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update addressing this vulnerability for Oracle E-Business Suite; until patch is available, restrict network access to Enterprise Command Center Framework HTTP interfaces using network segmentation and authentication controls.

Recommended fix Moderate confidence

Obtain the fixed version from Oracle Support - Oracle releases fixes via Critical Patch Updates (CPUs)

  1. Contact Oracle Support to obtain the specific patch or fixed version for this vulnerability
  2. Apply the latest Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses this vulnerability
  3. After patching, verify that the fix is applied by checking the Oracle Enterprise Command Center Framework version
  4. Validate that low-privileged users can no longer access unauthorized data or functions
Caveat Review Oracle's patch documentation for any known issues or required configuration changes before applying

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

Fix this in Enterprise Command Center Framework 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 help mitigating

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-46897 — 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-46897 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