dbcve.org
Webcenter PortalApplication · Oracle

CVE-2026-46844

CRITICAL · 9.9 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 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 Portal product of Oracle Fusion Middleware (component: Security Framework). 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 HTTPS to compromise Oracle WebCenter Portal. While the vulnerability is in Oracle WebCenter Portal, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Portal. 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 confidence

Critical vulnerability in Oracle WebCenter Portal's Security Framework allows low-privileged attackers with network access to achieve complete takeover of the portal. The CVSS 9.9 score indicates no user interaction required and high impact across confidentiality, integrity, and availability, with scope change potentially affecting additional Oracle products.

MitigationApply Oracle Critical Patch Updates for affected versions 12.2.1.4.0 and 14.1.2.0.0. If patches are unavailable, restrict network access to WebCenter Portal endpoints and review Security Framework configurations for workarounds.

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 PortalApplication
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
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 checks

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

  1. Confirm Oracle WebCenter Portal installation
    Look for Oracle WebCenter Portal processes running (such as WLS_WCP or WebCenter Portal-specific Java processes) or check for the product in Oracle Fusion Middleware inventory. On Windows, check services for 'Oracle WebCenter Portal' entries. On Unix/Linux, check for WebCenter processes or look in typical Oracle middleware installation paths like $ORACLE_HOME/webcenter.
    Affected if Oracle WebCenter Portal is not installed on the system.
  2. Verify installed version matches affected releases
    Check the WebCenter Portal version. This is typically available through the Oracle Enterprise Manager console, in the product's About page, or by inspecting the inventory file in the Oracle Middleware home. The affected versions are exactly 12.2.1.4.0 and 14.1.2.0.0.
    Affected if The installed version is 12.2.1.4.0 or 14.1.2.0.0 exactly.
  3. Confirm Security Framework component is in use
    Determine if the WebCenter Portal Security Framework is configured and active. This can be verified through the WebCenter Portal administration console under Security configurations, or by checking for security-related XML configuration files in the WebCenter deployment (typically in the portal's configuration directories).
    Affected if The Security Framework is enabled and configured for the portal.
  4. Assess network accessibility of WebCenter Portal
    Verify if the WebCenter Portal HTTP/HTTPS endpoints are exposed to the network. Check firewall rules, load balancer configurations, or reverse proxy settings that expose the portal. Attempt to reach the portal from an untrusted network segment if authorized.
    Affected if WebCenter Portal is accessible over the network to untrusted users or from untrusted networks.

If Oracle WebCenter Portal versions 12.2.1.4.0 or 14.1.2.0.0 are installed with Security Framework enabled and the portal is network-accessible, the environment is affected by this vulnerability.

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 affected versions 12.2.1.4.0 and 14.1.2.0.0. If patches are unavailable, restrict network access to WebCenter Portal endpoints and review Security Framework configurations for workarounds.

Fix this in Webcenter Portal 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-46844 — 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-46844 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