dbcve.org
Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-35285

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

Critical deserialization/remote code execution vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component, exploitable via T3 and IIOP protocols. Low-privileged network attackers can achieve complete system compromise, with scope potentially affecting additional products beyond Capture.

MitigationApply Oracle critical patch updates or upgrade to patched versions; restrict network access to T3/IIOP ports; consider disabling these protocols if not required for business functions.

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 if Oracle WebCenter Enterprise Capture is installed
    Check your system for Oracle WebCenter Enterprise Capture installation directories or inventory listings. Common locations include Oracle Fusion Middleware home directories. Look for the 'capture' component in your Oracle Middleware installation.
    Affected if The product is not installed on the system, this CVE does not apply.
  2. Determine the installed version of WebCenter Enterprise Capture
    Locate version information in the Capture installation directory, typically found in manifest files or version properties within the Capture home folder. Check the Oracle Inventory or use the Oracle OPatch lsinventory command if available.
    Affected if The installed version matches exactly 12.2.1.4.0 or exactly 14.1.2.0.0, indicating the system runs a known affected version.
  3. Check if T3 protocol is enabled
    Review WebCenter Enterprise Capture configuration files and WebLogic Server settings for T3 protocol listeners. T3 is typically configured in the WebLogic Administration Console under the Servers or Cluster configuration. Look for T3 or T3S protocol bindings in the configuration.
    Affected if T3 protocol is actively enabled and accessible on the network, creating the attack vector for deserialization exploitation.
  4. Check if IIOP protocol is enabled
    Review WebCenter Enterprise Capture and WebLogic configuration for IIOP protocol settings. Check the WebLogic Administration Console under the Servers configuration for IIOP enablement. Verify IIOP listener ports are open and configured.
    Affected if IIOP protocol is actively enabled and accessible on the network, creating an alternate attack vector for deserialization exploitation.
  5. Verify network exposure of T3/IIOP ports
    Identify and review open ports on systems running WebCenter Enterprise Capture. T3 typically uses port 7001 (default WebLogic), while IIOP uses port 28001. Use network scanning or port inspection tools to determine if these ports are exposed beyond internal networks.
    Affected if T3 or IIOP ports are accessible from untrusted or external network segments, allowing remote attackers to reach the vulnerable component.

A system is affected if Oracle WebCenter Enterprise Capture version 12.2.1.4.0 or 14.1.2.0.0 is installed AND either T3 or IIOP protocol is enabled and network-accessible to low-privileged attackers.

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 or upgrade to patched versions; restrict network access to T3/IIOP ports; consider disabling these protocols if not required for business functions.

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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