dbcve.org
Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-35281

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

This is a critical deserialization vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component. It is exploited via network access using Oracle WebLogic's T3 or IIOP protocols, allowing a low-privileged attacker to achieve remote code execution and complete system takeover. The attack vector (T3/IIOP) suggests insecure Java object deserialization, a well-documented vulnerability class in Oracle Fusion Middleware products.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for WebCenter Enterprise Capture to the affected versions (12.2.1.4.0, 14.1.2.0.0), or disable T3/IIOP protocols if not required, and restrict network access to the affected endpoints.

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 installation
    Check for the presence of Oracle WebCenter Enterprise Capture by looking for its installation directory (commonly under Oracle Middleware home/ Capture), or query the Oracle WebLogic Administration Console for deployed WebCenter Capture applications.
    Affected if The software is not installed - no further action needed. If installed, proceed to version check.
  2. Determine installed WebCenter Enterprise Capture version
    Locate the version information in the Capture installation: check the inventory file, or look for version metadata in the Capture deployment directory (such as MANIFEST.MF files), or query via WebLogic Administration Console under Deployments > Capture > Version.
    Affected if Version is exactly 12.2.1.4.0 OR 14.1.2.0.0 - continue to protocol check. Versions outside these two specific versions are NOT affected by this CVE.
  3. Confirm T3 protocol is enabled on WebLogic
    Check the WebLogic Server Administration Console: navigate to Domain > Security > Advanced, or inspect the WebLogic startup scripts (startWebLogic.cmd/.sh) for T3-related configuration. Alternatively, use WLST (WebLogic Scripting Tool) to query the server runtime for T3 protocol status.
    Affected if T3 protocol is explicitly enabled - the deserialization vulnerability is exploitable via this vector.
  4. Confirm IIOP protocol is enabled on WebLogic
    Check WebLogic Administration Console under Domain > Protocols > IIOP, or inspect the config.xml file for IIOP configuration, or query via WLST. Ensure both enable and globalIIOPEnabled attributes are reviewed.
    Affected if IIOP protocol is enabled - the deserialization vulnerability is exploitable via this vector.
  5. Assess network accessibility of affected endpoints
    Review firewall rules and network segmentation around the WebLogic servers hosting WebCenter Enterprise Capture. Verify whether T3/IIOP ports (default 7001 for admin, typically 7002-7005 for managed servers) are exposed to untrusted networks.
    Affected if The T3/IIOP ports are accessible from untrusted or public networks - the vulnerability can be exploited remotely.

A user is affected if they have WebCenter Enterprise Capture version 12.2.1.4.0 or 14.1.2.0.0 installed AND have T3 or IIOP protocols enabled on their WebLogic servers hosting this component, with those ports network-accessible to potential 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 the relevant Oracle Critical Patch Update (CPU) for WebCenter Enterprise Capture to the affected versions (12.2.1.4.0, 14.1.2.0.0), or disable T3/IIOP protocols if not required, and restrict network access to the affected endpoints.

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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