Weblogic ServerApplication · Oracle

CVE-2026-35259

HIGH · 8.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 →
95/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 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise WebLogic Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of WebLogic Server. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 WebLogic Server's Console component affecting versions 14.1.2.0.0 and 15.1.1.0.0. Attackers with network access via HTTPS can achieve complete takeover of the WebLogic Server by exploiting this flaw, but human interaction from a victim is required.

MitigationApply Oracle's official security patches for this vulnerability to WebLogic Server versions 14.1.2.0.0 and 15.1.1.0.0, or upgrade to a patched version. Until patched, restrict Console access to trusted networks only.

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:= 14.1.2.0.0= 15.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 WebLogic Server version
    Check the installed WebLogic Server version by inspecting the registry, installation directory, or running: java -jar wlserver_14.1.2.0.0/inventory/registry.xml or check the OPatch output: cd $ORACLE_HOME/OPatch && ./opatch lsinventory
    Affected if Installed version equals 14.1.2.0.0 or 15.1.1.0.0 exactly (these are the only affected versions)
  2. Verify Console component is enabled
    Check if the Administration Console is deployed and enabled by examining the config.xml file in the domain configuration directory (typically $DOMAIN_HOME/config/config.xml) for the presence of the Console descriptor, or check the WebLogic Administration Console login page is accessible
    Affected if Console component is deployed and accessible at the /console endpoint
  3. Confirm network accessibility of Console
    Determine if the Console is exposed to network access by reviewing the Listen Address setting in the server configuration (via WebLogic Administration Console > Servers > [ServerName] > General tab, or in config.xml), and test external access via: curl -k https://<host>:<port>/console
    Affected if Console listens on a non-localhost address and is reachable from untrusted networks over HTTPS

A user is affected if they have WebLogic Server version 14.1.2.0.0 or 15.1.1.0.0 installed WITH the Console component enabled AND exposed to network access, since the flaw requires both conditions plus victim interaction.

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's official security patches for this vulnerability to WebLogic Server versions 14.1.2.0.0 and 15.1.1.0.0, or upgrade to a patched version. Until patched, restrict Console access to trusted networks only.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-35259 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