dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-35298

CRITICAL · 9.1 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 →
97/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 WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows high privileged 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 9.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/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 · high confidence

Critical vulnerability in Oracle WebLogic Server's Core component (affecting versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0) that allows high privileged attackers with network access via HTTP to achieve complete takeover of the WebLogic Server. The vulnerability enables full confidentiality, integrity, and availability compromise and may impact additional products due to scope change.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability; if patches are unavailable, restrict network access to WebLogic Server administration interfaces and minimize high-privileged accounts.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify WebLogic Server installation
    Locate the WebLogic installation directory. Check for existence of ORACLE_HOME or Middleware home directories, typically under /oracle/weblogic, /u01/oracle/weblogic, or C:\Oracle\WebLogic on Windows. Look for thewlserver_*.jar installer remnants or registry entries.
    Affected if WebLogic Server is not installed, this CVE does not apply.
  2. Determine installed WebLogic version
    Check the version file in the WebLogic installation: view the PRODUCT_VERSION file in the ORACLE_HOME/wlserver_12.2 or wlserver_14.1 directory, or run: java -jar wlserver_14.1.1.0.0/bin/wlserver.jar -version. Alternatively, access the WebLogic Admin Console and check the 'Environment > Servers' page for version information.
    Affected if Installed version matches 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0, or falls within 12.2.1.4.0 through 15.1.1.0.0 range.
  3. Confirm HTTP network accessibility
    Review network configuration to determine if the WebLogic HTTP port (typically 7001 for admin, or application-specific ports) is exposed to network access. Check the Admin Console under 'Environment > Servers > [ServerName] > Listen Port' and review any external-facing load balancers or proxies. Inspect config.xml for network channel bindings.
    Affected if HTTP listen ports are accessible from untrusted networks (not restricted to localhost or trusted admin subnets).
  4. Verify high-privileged attacker scenario
    Assess whether attacker could obtain high-privileged access. Check if WLS admin console or WLST is accessible, review directory services integration (LDAP/AD), and check for weak or default credentials on admin accounts. Review audit logs for failed high-privilege authentication attempts.
    Affected if High-privileged WebLogic accounts exist and are accessible to potential attackers, or admin console is exposed on accessible networks.

You are affected if WebLogic Server is installed with version 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 (or any version in the 12.2.1.4.0 through 15.1.1.0.0 range), AND the HTTP administration port is network-accessible to untrusted users, AND a high-privileged attacker could potentially authenticate to the system.

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 (CPU) containing the fix for this vulnerability; if patches are unavailable, restrict network access to WebLogic Server administration interfaces and minimize high-privileged accounts.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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