dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-35302

HIGH · 8.3 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 →
90/100
Remediation priority · Urgent
Remotely reachable No privileges

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. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise WebLogic Server. Successful attacks require human interaction from a person other than the attacker and 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 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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

Unauthenticated remote code execution vulnerability in the Oracle WebLogic Server Console component, exploitable via HTTP network attack. Requires human interaction from a person other than the attacker and can lead to complete takeover of the WebLogic Server. The scope change indicates potential impact to additional products beyond WebLogic Server.

MitigationApply the Oracle Critical Patch Update addressing CVE-2026-35302 for versions 12.2.1.4.0 or 14.1.1.0.0; meanwhile, restrict network access to the WebLogic Console to trusted networks and disable console access if not required.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 WebLogic installation by checking common directories (Oracle/Middleware, Oracle/Home) or running process inspection. On Windows, check services for 'Oracle WebLogic' entries. On Unix/Linux, look for WebLogic processes using 'ps -ef | grep -i weblogic' or check for installation paths under /opt/oracle, /u01, or similar.
    Affected if WebLogic Server is installed and running
  2. Determine installed WebLogic version
    Check the version using the WebLogic Administration Server startup logs (typically in servers/AdminServer/logs/AdminServer.log) or by inspecting the inventory file. You can also use the 'java -cp weblogic.jar weblogic.version' command from the WebLogic home directory.
    Affected if Version is exactly 12.2.1.4.0 or 14.1.1.0.0
  3. Verify Console component is enabled
    Confirm the WebLogic Administration Console is accessible. Default console URL is http://localhost:7001/console (or the configured Admin Server port). Check server configuration in config/config.xml for the AdminServer listening on the console port.
    Affected if Console component is accessible and responding on the configured HTTP port for the Admin Server
  4. Check network exposure of Admin Server port
    Review firewall rules, network configuration, and WebLogic Server network channel settings. Determine if the Admin Server port (default 7001) is bound to 0.0.0.0 or an external network interface rather than localhost only. Use 'netstat -an | grep 7001' or 'ss -tlnp | grep 7001' to check listening addresses.
    Affected if Console port is listening on external/network interfaces accessible from untrusted networks

Environment is affected if WebLogic Server versions 12.2.1.4.0 or 14.1.1.0.0 are installed with the Administration Console component enabled and exposed to network access.

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 the Oracle Critical Patch Update addressing CVE-2026-35302 for versions 12.2.1.4.0 or 14.1.1.0.0; meanwhile, restrict network access to the WebLogic Console to trusted networks and disable console access if not required.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update containing fix for CVE-2026-35302; contact Oracle Support for specific patch availability

  1. Check Oracle Critical Patch Updates (CPU) for the most recent security patches affecting WebLogic Server 12.2.1.4.0 and 14.1.1.0.0
  2. Apply the latest Oracle CPU patch that addresses CVE-2026-35302 or the Console open redirect vulnerability
  3. Alternatively, contact Oracle Support directly to request the specific patch for this vulnerability
  4. After patching, verify the Console redirect functionality works correctly and no longer allows arbitrary URL redirection
  5. Restrict network access to the WebLogic Server Console to trusted networks only as an interim mitigation
Caveat Standard Oracle CPU patching typically has minimal risk; test in non-production environment first

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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