CVE-2026-35303
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 · uneditedVulnerability 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 low privileged attacker with network access via HTTP to compromise WebLogic Server. 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:L/UI:N/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 confidenceOracle WebLogic Server Console component has a vulnerability allowing low-privileged remote attackers to achieve complete system takeover via HTTP. The vulnerability affects versions 12.2.1.4.0 and 14.1.1.0.0 with network exploitability requiring no user interaction.
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= 12.2.1.4.0= 14.1.1.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate WebLogic Server installationCheck common installation directories such as $ORACLE_HOME, /u01/oracle/weblogic, or C:\Oracle\Middleware, and look for the wlserver directory structure.Affected if WebLogic Server is installed in any directory on the system.
-
Identify installed WebLogic Server versionIn the installation directory, locate the file PRODUCT_HOME/wlserver_14.1.1.0/server/lib/weblogic.jar or check the inventory file for the exact version string. Run: java -jar wlserver_14.1.1.0/server/lib/weblogic.jar -versionAffected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.1.0.0.
-
Verify Console component is enabledCheck the WebLogic Server configuration file config.xml in the domain directory for a <console-enabled>true</console-enabled> entry under the Administration Server configuration, or attempt to access the Console URL (typically port 7001/7002 at /consoleAffected if The Console is enabled and accessible on the network.
-
Confirm network exposure of ConsoleReview the Administration Server network listen address in config.xml. Check if the listen-address is set to 0.0.0.0 or a publicly accessible IP, and verify firewall rules allow access to the Console port from untrusted networks.Affected if The Console listens on all interfaces (0.0.0.0) or is accessible from untrusted network segments.
A system is affected if it runs Oracle WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with the Console component enabled and network accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Updates for WebLogic Server or implement network segmentation/restrict Console access until patches can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35303 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35303 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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