dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-35326

HIGH · 7.2 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 →
78/100
Remediation priority · High
Remotely reachable 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 high privileged 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 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/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

Vulnerability in Oracle WebCenter Content Content Server allows high privileged attackers with network access via HTTP to achieve complete takeover of the affected system. The CVSS vector indicates high confidentiality, integrity, and availability impacts, and the description explicitly states 'takeover' is possible.

MitigationApply Oracle security patches for WebCenter Content versions 12.2.1.4.0 and 14.1.2.0.0. As an easily exploitable vulnerability allowing complete system takeover, prioritize patching given the high CVSS score and network accessibility.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Oracle WebCenter Content version
    Access the Oracle WebCenter Content admin interface and navigate to the About or System Information page, or check the installation directory for version files. The version is typically displayed in the Content Server admin console or can be retrieved via command line tools in the installation bin directory.
    Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  2. Confirm Content Server component is running
    Verify that the Oracle Content Server service is active. This can be checked via the Oracle WebLogic Server administration console, by querying running Java processes, or by checking the Content Server status page accessible via the web interface.
    Affected if Content Server is running and accessible via HTTP network access
  3. Verify network accessibility of Content Server
    Confirm that the Content Server HTTP listener is bound to a network-accessible interface. Check the WebLogic configuration for the Content Server managed server and verify the listen address and port settings. Test network connectivity to the server from external hosts.
    Affected if Content Server is reachable over HTTP from network locations, as the vulnerability requires network access via HTTP

A system is affected if it runs Oracle WebCenter Content version 12.2.1.4.0 or 14.1.2.0.0 with the Content Server component enabled and accessible over HTTP from the network.

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 security patches for WebCenter Content versions 12.2.1.4.0 and 14.1.2.0.0. As an easily exploitable vulnerability allowing complete system takeover, prioritize patching given the high CVSS score and network accessibility.

Recommended fix Moderate confidence

Oracle recommends applying the relevant CPU patch; for major version upgrade, Oracle WebCenter Content 12c (12.2.1.x) and 14c (14.x) have subsequent patches beyond 12.2.1.4.0 and 14.1.2.0.0 that contain security fixes

  1. Check the Oracle Critical Patch Update (CPU) advisory for the quarter containing this CVE to identify the specific patch number for WebCenter Content
  2. Navigate to Oracle Support (support.oracle.com) and search for the CVE or WebCenter Content security patches
  3. Download and apply the relevant security patch following Oracle's standard patch application procedures
  4. After patching, restart the Content Server component as required by the patch
  5. Verify the patch was applied successfully by checking the system and reviewing Oracle's patch documentation
  6. Test critical Content Server functionality to ensure normal operation after the update
Caveat Oracle patches are typically cumulative; review patch readme for any specific configuration or restart requirements

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

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-35326 — 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-35326 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