dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-46766

CRITICAL · 9.8 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 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 Content product of Oracle Fusion Middleware (component: Content Server). 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 HTTP to compromise Oracle WebCenter Content. Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Content. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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

Unauthenticated remote code execution vulnerability in Oracle WebCenter Content Server component. Easily exploitable via HTTP without any authentication, allowing complete system takeover including full confidentiality, integrity, and availability compromise.

MitigationApply Oracle patch for affected versions 12.2.1.4.0 and 14.1.2.0.0 immediately. Until patched, restrict network access to Content Server via firewall or network segmentation.

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 ContentApplication
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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Content is installed
    Check for running processes named 'ContentServer', 'ucm', or 'oracle.ucm' on the system, or look for WebCenter Content installation directories (typically under $ORACLE_HOME/ucm or similar paths)
    Affected if The product is present and running on the system
  2. Determine the installed version
    Access the WebCenter Content administration interface (typically at /idc/login.jsp or /cs/idc/login.jsp) and check the 'About' page, or check version files in the installation directory such as ucm/shared/config/ucm.cs or registry.xml
    Affected if The version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  3. Confirm HTTP interface is exposed
    Verify the WebCenter Content HTTP listener is accessible on the configured port (default 16200 or 8080). Attempt to reach the login page via browser or curl: curl -k https://<host>:<port>/cs/idc/login.jsp
    Affected if The HTTP/HTTPS interface is accessible over the network (not blocked by firewall)
  4. Check if unauthenticated requests are possible
    Send a request to the Content Server without providing credentials, for example: curl -k 'https://<host>:<port>/cs/idc/service/'
    Affected if The server accepts and processes unauthenticated requests to the service endpoints

If the installed version is exactly 12.2.1.4.0 or 14.1.2.0.0 AND the HTTP interface is network-accessible, the environment is vulnerable to unauthenticated RCE.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle patch for affected versions 12.2.1.4.0 and 14.1.2.0.0 immediately. Until patched, restrict network access to Content Server via firewall or network segmentation.

Recommended fix Moderate confidence

Apply latest Oracle Critical Patch Update (CPU) containing the fix for CVE-2026-46766; Oracle typically includes WebCenter Content fixes in quarterly CPU releases

  1. Check Oracle's Critical Patch Updates (CPUs) for the nearest quarterly release after the vulnerability disclosure date
  2. Download and apply the latest Oracle WebCenter Content patch from Oracle Support (support.oracle.com)
  3. If no CPU is available, contact Oracle for an out-of-cycle patch
  4. After patching, verify the fix by reviewing applied patches via Oracle Enterprise Manager or command-line tools
  5. Restrict network access to Content Server to minimize attack surface until patch is applied
Caveat Review Oracle CPU release notes for any post-installation steps or known issues specific to WebCenter Content before applying

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

Fix this in Webcenter Content Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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 locally
dbcve dependency scanner

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