dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-35301

CRITICAL · 10.0 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 WebLogic Server product of Oracle Fusion Middleware (component: Console). Supported versions that are affected are 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise WebLogic Server. While the vulnerability is in WebLogic Server, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of WebLogic Server. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 unauthenticated remote code execution vulnerability in Oracle WebLogic Server Console (versions 12.2.1.4.0 and 14.1.1.0.0) allows remote attackers with HTTP network access to achieve complete takeover of the WebLogic Server. The CVSS 10 score indicates trivial exploitability (network-based, no privileges or user interaction required) with scope expansion to additional products and full confidentiality/integrity/availability impact.

MitigationApply Oracle Critical Patch Update immediately; if patches are unavailable, restrict network access to the WebLogic Console to trusted IPs only or disable console access until patched.

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
Weblogic ServerApplication
Affected:= 12.2.1.4.0= 14.1.1.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify WebLogic Server installation
    Locate the WebLogic installation directory. Common paths include $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver. Check for the existence of the wlserver directory structure.
    Affected if WebLogic Server is installed on the system
  2. Determine installed WebLogic version
    Check the version file in the installation directory. Look for a file named 'version.txt' or 'registry.xml' in the wlserver directory. Alternatively, access the WebLogic Administration Console and check the 'Server' > 'Monitoring' > 'General' page for the version information.
    Affected if Installed version matches exactly 12.2.1.4.0 or 14.1.1.0.0
  3. Verify WebLogic Console is enabled
    Check the configuration file 'config.xml' in the domain directory (typically in $DOMAIN_HOME/config/config.xml). Search for <console-enabled> or similar console configuration elements. Also check if the console war deployment exists in the domain.
    Affected if WebLogic Console is enabled and deployed
  4. Confirm console network accessibility
    Review network listeners and ports configured for the WebLogic Server. Check the 'config.xml' for <listen-address> settings and verify which network interfaces the administration port is bound to. Test connectivity by attempting HTTP access to the console URL (typically /console) from an external host.
    Affected if Console is reachable over HTTP from untrusted network locations

A system is affected if it runs WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with the administration console enabled and accessible over a 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update immediately; if patches are unavailable, restrict network access to the WebLogic Console to trusted IPs only or disable console access until patched.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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