CVE-2026-46782
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 HTTP 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 confidenceVulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component allows low-privileged attackers with network access via HTTP to achieve complete takeover of the affected system. The CVSS 9.9 score indicates trivial exploitability with total confidentiality, integrity, and availability compromise, and the scope change indicates attacks may cascade to additional 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.
-
Verify Oracle WebCenter Enterprise Capture is installedCheck for WebCenter Capture installation directories (commonly under Oracle middleware home) or look for the capture service/process running on the systemAffected if WebCenter Enterprise Capture software is present on the system
-
Confirm the installed version matches affected releasesLocate the version file or check the Oracle Enterprise Manager/Admin Console for the exact WebCenter Capture version numberAffected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
-
Identify if Client Bundle component is exposedCheck the WebCenter Capture admin console or configuration files for Client Bundle endpoint accessibility; verify if client download/distribution features are enabledAffected if Client Bundle component is accessible and accepts network connections from untrusted users
-
Assess network accessibility of the affected serviceReview firewall rules, reverse proxy configurations, and network ACLs to determine if the WebCenter Capture interface is reachable from untrusted network segmentsAffected if The Capture service port/interface is exposed to network segments accessible by low-privileged attackers without authentication barriers
You are affected if Oracle WebCenter Enterprise Capture versions 12.2.1.4.0 or 14.1.2.0.0 is installed with the Client Bundle component accessible over the network to untrusted users.
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.
dbcve · scopedApply Oracle Critical Patch Update patches for WebCenter Enterprise Capture versions 12.2.1.4.0 and 14.1.2.0.0 when released; restrict HTTP/HTTPS access to authorized personnel until patch deployment.
Oracle WebCenter Enterprise Capture 14.1.3.0 or later (which includes the fix in the CPU that addresses this CVE)
- 1. Review the Oracle Critical Patch Update (CPU) advisory for the quarter that addresses CVE-2026-46782
- 2. Identify the appropriate patch for Oracle WebCenter Enterprise Capture 12.2.1.4.0 or 14.1.2.0.0 from the Oracle Patch Update
- 3. Download the patch from Oracle Support (support.oracle.com) using the patch ID from the CPU advisory
- 4. Apply the patch following Oracle's standard patch application procedures for WebCenter Enterprise Capture
- 5. After patching, verify the Client Bundle component is updated and test that normal capture functionality works
- 6. Restart the WebCenter Enterprise Capture services as required by the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,384.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46782 — 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-46782 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