Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-35280

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 vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component, exploitable via T3/IIOP network protocols. Low-privileged attackers can achieve complete system takeover over the network with no user interaction, with potential scope impact to additional products.

MitigationApply Oracle Critical Patch Update (CPU) patches for WebCenter Enterprise Capture 12.2.1.4.0 and 14.1.2.0.0. As interim mitigation, restrict or disable T3/IIOP network access and implement network segmentation around affected systems.

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
    Locate the WebCenter Enterprise Capture installation directory or check for running Java processes related to Capture (look for Oracle ECM or Capture processes in process lists)
    Affected if The product is not installed - if not present, this CVE does not apply
  2. Determine the installed version
    Check the version of WebCenter Enterprise Capture by examining the installation manifest, About dialog in the admin console, or version file in the product directory. Compare against affected versions 12.2.1.4.0 and 14.1.2.0.0
    Affected if Installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0 - these are the affected versions listed
  3. Verify T3/IIOP protocol exposure
    Review the WebCenter Enterprise Capture configuration files (typically in the config directory) and WebLogic server configuration for enabled protocols. Check if T3 or IIOP protocols are enabled on the listening ports
    Affected if T3 and/or IIOP protocols are enabled and accessible - this is the attack vector required for exploitation
  4. Assess network accessibility of affected ports
    Scan or probe the network ports used by WebCenter Enterprise Capture (typically 7001 for admin console, plus T3/IIOP ports) from untrusted network segments to determine if the service is exposed
    Affected if T3/IIOP ports are accessible from network segments outside the trusted zone - this determines whether an external low-privileged attacker can reach the vulnerability

A system is affected if WebCenter Enterprise Capture versions 12.2.1.4.0 or 14.1.2.0.0 are installed with T3/IIOP protocols enabled and accessible from the attacker's network location.

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 WebCenter Enterprise Capture 12.2.1.4.0 and 14.1.2.0.0. As interim mitigation, restrict or disable T3/IIOP network access and implement network segmentation around affected systems.

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-35280 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