dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-35263

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 WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows low 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.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 · high confidence

Critical vulnerability in Oracle WebLogic Server's Core component (versions 14.1.2.0.0 and 15.1.1.0.0) allowing low-privileged remote attackers with HTTP network access to achieve complete server takeover. The CVSS scope change indicates attacks may significantly impact additional products beyond WebLogic itself.

MitigationApply Oracle critical patch updates for WebLogic Server immediately. As immediate compensating controls, restrict network access to HTTP/HTTPS ports and disable unnecessary network exposed services until patches are deployed.

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
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. Locate WebLogic Server installation
    Search for Oracle WebLogic Server installation directories, typically under $ORACLE_HOME or common paths like /opt/oracle/weblogic, C:\Oracle\WebLogic, or /u01/app/oracle/product/weblogic. Check for folders containing 'wlserver' or 'coherence' subdirectories.
    Affected if WebLogic Server is not installed on the system.
  2. Identify installed WebLogic version
    Check the version file in the WebLogic installation directory. Common locations: <WL_HOME>/registry.xml, <WL_HOME>/.product_version, or look for VERSION.txt in the installation root. Alternatively, access the WebLogic Administration Console via HTTP/HTTPS and check the 'About' page, or use WLST (WebLogic Scripting Tool) with command: java weblogic.WLST -printObjName -c 'print domainRuntimeService.getServerRuntime().getWebLogicVersion()'
    Affected if The installed version is exactly 14.1.2.0.0 or exactly 15.1.1.0.0.
  3. Verify HTTP network listener is enabled
    Log into WebLogic Administration Console, navigate to 'Servers' > 'your_server' > 'General' tab, and confirm 'Listen Port' is enabled (typically port 7001). From command line, check config.xml in the domain directory for <listen-port> entries under <server> elements.
    Affected if HTTP/HTTPS listen ports are configured and enabled on the affected server.
  4. Confirm network accessibility
    Check if the WebLogic listen port (default 7001 for admin, or configured port) is exposed to network accessible IPs. Review firewall rules, load balancer configurations, or OHS (Oracle HTTP Server) front-end settings. Use netstat -an | grep 7001 or equivalent to confirm the port is listening on non-loopback interfaces.
    Affected if The WebLogic HTTP port is reachable from network addresses outside localhost or trusted management networks.

You are affected if Oracle WebLogic Server version 14.1.2.0.0 or 15.1.1.0.0 is installed with HTTP network listeners accessible to untrusted networks.

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 WebLogic Server immediately. As immediate compensating controls, restrict network access to HTTP/HTTPS ports and disable unnecessary network exposed services until patches are deployed.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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