dbcve.org
Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-46779

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 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 low privileged attacker with network access via T3 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 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 deserialization vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component. Low-privileged attackers with network access via the T3 protocol (Oracle WebLogic RMI) can achieve remote code execution and complete system takeover. The scope change indicates attacks can impact additional Oracle products in the environment.

MitigationApply Oracle Critical Patch Update (CPU) addressing this vulnerability; restrict T3/IIOP protocol access via network segmentation or WebLogic channel configuration; if patches unavailable, consider disabling T3 listeners or upgrading to patched version.

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
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 Oracle WebCenter Enterprise Capture installation
    Search for WebCenter Enterprise Capture installation directories or check for the 'capture' application component in Oracle WebLogic Server domain configurations. Look for the product in Oracle inventory files or WebLogic deployment manifests.
    Affected if Oracle WebCenter Enterprise Capture is installed and the version matches 12.2.1.4.0 or 14.1.2.0.0
  2. Confirm installed version
    Locate version information in the product's manifest, Oracle inventory, or WebLogic console for the WebCenter Enterprise Capture deployment. Compare against the affected versions.
    Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
  3. Verify T3 protocol listener is accessible
    Check WebLogic Server configuration for enabled T3 or T3S listeners. Review network listeners in the WebLogic Administration Console or config.xml. Use network scanning to confirm port 7001 (default T3) or custom T3 ports are accepting connections.
    Affected if T3 protocol listener is enabled and network-accessible to untrusted actors
  4. Check Client Bundle component status
    Examine the WebCenter Enterprise Capture deployment configuration in WebLogic to determine if the Client Bundle component is deployed and active. Look for client-bundle related resources in the application configuration.
    Affected if The Client Bundle component of WebCenter Enterprise Capture is deployed and running

A user is affected if they have Oracle WebCenter Enterprise Capture version 12.2.1.4.0 or 14.1.2.0.0 installed with the Client Bundle component enabled and an accessible T3 protocol listener.

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 Update (CPU) addressing this vulnerability; restrict T3/IIOP protocol access via network segmentation or WebLogic channel configuration; if patches unavailable, consider disabling T3 listeners or upgrading to patched version.

Recommended fix Moderate confidence

Latest available version of Oracle WebCenter Enterprise Capture (version > 14.1.2.0.0) following Oracle's CPU release

  1. Check Oracle's official Critical Patch Update (CPU) advisory for the security fix addressing CVE-2026-46779
  2. Download and apply the latest Oracle Critical Patch Update for WebCenter Enterprise Capture
  3. If CPU patch is not available, upgrade Oracle WebCenter Enterprise Capture to the next available version higher than 14.1.2.0.0
  4. After upgrade, verify the T3 protocol listener configuration and restrict network access to trusted sources
  5. Restart the WebCenter Enterprise Capture services to apply the fix
Caveat Review Oracle's upgrade documentation for changes between 12.2.1.4.0/14.1.2.0.0 and the target version, particularly around T3 protocol configuration and client bundle settings

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

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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