dbcve.org
Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-46778

CRITICAL · 10.0 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 No privileges 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 WebCenter Enterprise Capture product of Oracle Fusion Middleware (component: Client Bundle). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via RMI to compromise Oracle WebCenter Enterprise Capture. While the vulnerability is in Oracle WebCenter Enterprise Capture, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Enterprise Capture. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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

A critical deserialization or remote code execution vulnerability exists in Oracle WebCenter Enterprise Capture's Client Bundle component. The flaw is exploitable remotely via RMI without authentication, allowing a complete system takeover. The CVSS 10 score reflects complete confidentiality, integrity, and availability compromise.

MitigationApply Oracle Critical Patch Updates when released for versions 12.2.1.4.0 and 14.1.2.0.0. As an immediate workaround, restrict network access to RMI ports or disable unnecessary RMI endpoints until patching is possible.

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
Webcenter Enterprise CaptureApplication
Affected:= 12.2.1.4.0= 14.1.2.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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 WebCenter Enterprise Capture is installed
    Check for Oracle WebCenter Enterprise Capture installation directories, services, or installed packages on the system. Common locations include Oracle Fusion Middleware home directories.
    Affected if The product is installed on the system
  2. Determine the installed version of Oracle WebCenter Enterprise Capture
    Locate version information in the installation directory, typically found in product configuration files, manifest files, or version-specific directories under the Oracle home. Compare the installed version against the affected versions 12.2.1.4.0 and 14.1.2.0.0.
    Affected if The installed version matches 12.2.1.4.0 or 14.1.2.0.0 exactly
  3. Verify if Client Bundle component is deployed
    Check the Oracle WebCenter Enterprise Capture deployment configuration for the presence and status of the Client Bundle component. This is typically configured in the WebCenter Capture admin console or deployment descriptors.
    Affected if Client Bundle component is enabled or deployed
  4. Confirm RMI network protocol is exposed
    Identify if RMI endpoints are configured and listening on network interfaces. Check Oracle WebCenter Capture network configuration files and listening ports. RMI typically uses ports in the dynamic range or configured JRMP ports.
    Affected if RMI protocol is enabled and accessible over the network on any interface
  5. Assess network accessibility of RMI endpoints
    Review network firewall rules, Oracle WebLogic server network configuration, and port bindings to determine if RMI endpoints are reachable from untrusted networks. Check if network access restrictions are in place.
    Affected if RMI endpoints are accessible from unauthenticated or untrusted network segments

A system is affected if Oracle WebCenter Enterprise Capture versions 12.2.1.4.0 or 14.1.2.0.0 are installed with the Client Bundle component enabled and RMI endpoints exposed to accessible network paths.

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 Oracle Critical Patch Updates when released for versions 12.2.1.4.0 and 14.1.2.0.0. As an immediate workaround, restrict network access to RMI ports or disable unnecessary RMI endpoints until patching is possible.

Recommended fix Moderate confidence
  1. Check My Oracle Support (support.oracle.com) for the specific patch for CVE-2026-46778 for Oracle WebCenter Enterprise Capture
  2. Apply the Oracle Critical Patch Update (CPU) that addresses this vulnerability
  3. If no specific patch is available, upgrade to the latest available Oracle WebCenter Enterprise Capture version
  4. As an immediate network-level mitigation, restrict or block network access to RMI ports (typically ports 7001-7005 or custom RMI ports) from untrusted sources
  5. Verify the capture environment is not exposed to untrusted network segments

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

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46778 — 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-46778 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