CVE-2026-35284
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 · uneditedVulnerability 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 · moderate confidenceAuthenticated remote code execution vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component, exploitable via T3/IIOP protocols. Low-privilege attackers can achieve complete system compromise (Confidentiality/Integrity/Availability: High) with network access, and the scope change indicates potential impact to additional Oracle products.
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= 12.2.1.4.0= 14.1.2.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle WebCenter Enterprise Capture installationSearch for WebCenter Enterprise Capture directories or check Oracle Fusion Middleware inventory files (typically under $ORACLE_HOME). Look for 'capture' or 'ecapture' folder names in the Oracle middleware directory structure.Affected if Oracle WebCenter Enterprise Capture software is present on the system
-
Determine installed WebCenter Enterprise Capture versionCheck the version file in the installation directory, typically found in the Client Bundle component path. Common locations include ORACLE_HOME/capture/client/version.txt or the inventory files in $ORACLE_HOME/inventory/ContentsXML/oracle_product.xml.Affected if Installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
-
Verify T3/IIOP protocol availabilityCheck WebLogic server configuration files (config.xml) or the WebLogic Administration Console for T3/IIOP protocol enablement. These protocols are typically enabled by default on WebLogic servers that host the Client Bundle component.Affected if T3 or IIOP protocols are enabled and accessible on the target server
-
Confirm network exposure of T3/IIOP portsIdentify the listening ports for T3 (typically 7001 default) and IIOP (typically 7002 default) using netstat or by reviewing WebLogic server configuration. Verify if these ports are exposed to untrusted networks.Affected if T3/IIOP ports are reachable from network segments accessible to low-privilege attackers
User is affected if Oracle WebCenter Enterprise Capture versions 12.2.1.4.0 or 14.1.2.0.0 are installed AND the T3/IIOP protocols are enabled and network-accessible to authenticated attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict network access to T3/IIOP ports; apply Oracle Critical Patch Updates when available; if patches are not yet released, consider disabling or firewall-blocking these protocols until remediation is possible.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35284 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35284 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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