dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-35286

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's Content Server component. Attackers can exploit this via HTTP network access to achieve complete system takeover without any credentials, affecting versions 12.2.1.4.0 and 14.1.2.0.0.

MitigationApply Oracle Critical Patch Updates for WebCenter Content version 12.2.1.4.0 or 14.1.2.0.0 immediately. If patching is not immediately possible, restrict network access to Content Server endpoints via firewall or web application firewall.

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. Identify if Oracle WebCenter Content is installed
    Look for the Oracle WebCenter Content installation directory, or check for processes named 'ContentServer' or 'ucm' running on the system. On Linux/Unix, run 'ps -ef | grep -i ucm' or 'ps -ef | grep -i content' to find related Java processes.
    Affected if No Oracle WebCenter Content installation is found - not affected by this CVE.
  2. Determine the installed version of Oracle WebCenter Content
    Check the version file in the installation directory. Common paths include <install_dir>/oracle_common/modules/oracle.ucm/ucm_server/bin/version.txt or look at the About dialog in the Content Server admin interface. You can also query the Content Server via the 'idc' service endpoint with '?service=admin&action=about'.
    Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0 - this CVE applies to those specific versions.
  3. Verify the Content Server component is enabled
    Check if the Content Server (formerly UCM) web application is deployed and running. Access the Content Server admin interface at the typical path '/cs/' or '/idc/' and confirm the service is responsive. Check application server (WebLogic, IBM WebSphere) console for deployed WebCenter Content applications.
    Affected if Content Server component is not deployed or not running - the vulnerability cannot be exploited.
  4. Assess network exposure of Content Server
    Determine if the Content Server HTTP/HTTPS ports are accessible from untrusted networks. Check firewall rules, load balancer configurations, and web server proxy settings. Verify if the server is directly exposed to the internet or only accessible within an internal network.
    Affected if Content Server is accessible from untrusted network sources via HTTP/HTTPS - exploitation is possible without authentication.

You are affected if Oracle WebCenter Content is installed, the version is exactly 12.2.1.4.0 or 14.1.2.0.0, the Content Server component is enabled, and the HTTP interface is reachable from a network where untrusted actors could send requests.

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 Updates for WebCenter Content version 12.2.1.4.0 or 14.1.2.0.0 immediately. If patching is not immediately possible, restrict network access to Content Server endpoints via firewall or web application firewall.

Fix this in Webcenter Content Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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