Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-46781

CRITICAL · 10.0 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 No privileges Zero-click

Official description

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 unauthenticated attacker with network access via RMI 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 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Technical summary

dbcve analysis · high confidence

Critical RMI-based remote code execution vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component. Unauthenticated attackers with network access can exploit this flaw to achieve full system compromise, including complete confidentiality, integrity, and availability impacts.

MitigationApply Oracle Critical Patch Updates for WebCenter Enterprise Capture versions 12.2.1.4.0 and 14.1.2.0.0. If patches are unavailable, restrict network access to RMI ports and implement network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Webcenter Enterprise CaptureApplication

Affected:= 12.2.1.4.0= 14.1.2.0.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if Oracle WebCenter Enterprise Capture is installed

Check for the product in Oracle inventory directories (e.g., $ORACLE_HOME/oraInventory/ContentsXML/oraclehome.xml) or look for installation directories containing 'Oracle_WC1' or 'capture' in the ORACLE_HOME path

Affected if Oracle WebCenter Enterprise Capture is found on the system
Determine the installed version of Oracle WebCenter Enterprise Capture

Locate the version file in the product installation directory, commonly found in the 'VERSION' file or 'registry.xml' within the ORACLE_HOME/Oracle_WC1/capture directory, or query the Oracle inventory using 'opatch lsinventory' if available

Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
Verify if Client Bundle component with RMI is enabled

Check the WebCenter Capture configuration files (e.g., capture-config.xml or deployment descriptors) for Client Bundle service definitions and RMI registry bindings. Look for entries referencing 'ClientBundle' or 'rmi' protocol handlers in the configuration

Affected if Client Bundle RMI service is configured and enabled in the capture environment
Assess network exposure of RMI ports

Review firewall rules, network configuration, and listener settings to determine if RMI ports (typically dynamic or configured in the 23791-23799 range for Oracle products) are accessible from untrusted networks. Use 'netstat -an | grep -E "2379[0-9]"' or similar to identify listening RMI ports

Affected if RMI ports are exposed to network segments accessible by unauthenticated attackers

A user is affected if Oracle WebCenter Enterprise Capture versions 12.2.1.4.0 or 14.1.2.0.0 are installed with the Client Bundle RMI component enabled and accessible over the network to unauthenticated parties.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Updates for WebCenter Enterprise Capture versions 12.2.1.4.0 and 14.1.2.0.0. If patches are unavailable, restrict network access to RMI ports and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

Latest supported 12.2.x or 14.x version of Oracle WebCenter Enterprise Capture (contact Oracle Support for exact version)

1. Identify the current Oracle WebCenter Enterprise Capture installation version and confirm it is either 12.2.1.4.0 or 14.1.2.0.0
2. Review Oracle's official Critical Patch Update advisories for the fix to CVE-2026-46781 at oracle.com/security-alerts
3. Download and apply the appropriate patch from Oracle Support (My Oracle Security) for the specific version
4. Alternatively, upgrade to a newer supported version of Oracle WebCenter Enterprise Capture that includes the security fix
5. After applying the patch or upgrade, restart the WebCenter Enterprise Capture services
6. Verify the RMI interface now requires proper authentication
7. Test that legitimate client connections to the Client Bundle component work correctly post-fix

Caveat Review Oracle's upgrade documentation for any configuration or compatibility changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webcenter Enterprise Capture Scoped from the published advisory

Consultation6.0 h
Implementation12.0 h
Testing12.0 h
Review / QA6.0 h

36.0 hours of engineering $6,240

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46781 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-46781?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 10.0 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Webcenter Enterprise Capture

Remediation

A high-priority fix

Fix this in Webcenter Enterprise Capture 36 hrs · High

Typical engagement from $6,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-46781 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References