dbcve.org
Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-35283

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, IIOP 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

Deserialization vulnerability in Oracle WebCenter Enterprise Capture Client Bundle allows low-privileged attackers with network access via T3 or IIOP protocols to achieve remote code execution and complete system compromise. The attack leverages insecure handling of serialized objects in the affected component, enabling full takeover of the Capture service with potential scope expansion to other integrated products.

MitigationApply Oracle Critical Patch Update (CPU) patches for versions 12.2.1.4.0 and 14.1.2.0.0; as interim mitigation, restrict or disable T3/IIOP network protocols and limit network exposure to the Capture service.

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. Verify Oracle WebCenter Enterprise Capture is installed
    Check for WebCenter Enterprise Capture installation by querying the Oracle inventory (目_inventory.xml) or looking for the Capture application directory under the Oracle middleware home. On Linux/Unix, typical path is $ORACLE_HOME/capture. On Windows, check the Oracle directory structure.
    Affected if Oracle WebCenter Enterprise Capture is found on the system
  2. Determine the Client Bundle component version
    Locate the Client Bundle JAR file or check the installed version through the Oracle WebCenter Enterprise Capture administration console, or query the Oracle inventory for the exact version number of the Capture component.
    Affected if The installed version is exactly 12.2.1.4.0 or 14.1.2.0.0
  3. Check if T3 protocol is enabled
    Examine the WebLogic Server configuration (config.xml) for the Managed Servers or Admin Server hosting the Capture application. Look for <protocol>T3</protocol> or similar T3 protocol definitions in the network channel configuration.
    Affected if T3 protocol is enabled and exposed on a listening port
  4. Check if IIOP protocol is enabled
    Review the WebLogic Server configuration for IIOP settings in the server's MBean attributes or config.xml. Look for IIOP-specific network channel configurations.
    Affected if IIOP protocol is enabled and exposed on a listening port
  5. Verify network exposure of T3/IIOP ports
    Scan for open ports associated with T3 (typically 7001, 7002) and IIOP (typically 2801-2809) using netstat or nmap, then determine if these ports are accessible from untrusted networks rather than only localhost.
    Affected if T3 or IIOP ports are accessible from network segments outside the trusted internal network

The environment is affected if Oracle WebCenter Enterprise Capture Client Bundle versions 12.2.1.4.0 or 14.1.2.0.0 are installed AND T3/IIOP protocols are enabled and network-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.

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

Apply Oracle Critical Patch Update (CPU) patches for versions 12.2.1.4.0 and 14.1.2.0.0; as interim mitigation, restrict or disable T3/IIOP network protocols and limit network exposure to the Capture service.

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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