CVE-2026-35299
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 contains a vulnerability allowing low-privileged attackers with network access via HTTP to achieve complete takeover of the server. The vulnerability affects versions 12.2.1.4.0 and 14.1.1.0.0 and is described as easily exploitable, indicating a straightforward attack path.
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.
-
Confirm WebLogic Server installationLocate the WebLogic installation directory and identify the domain configuration. Common paths include $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver. Check for the presence of the 'console' application in the domains/yourdomain/applications directory.Affected if WebLogic Server is not installed, then the CVE does not apply.
-
Identify WebLogic Server versionCheck the version by examining the manifest file in the wlserver directory, or by accessing the WebLogic Console footer which displays the version number. The version is also visible in the admin server log file upon startup.Affected if The installed version matches 12.2.1.4.0 or 14.1.1.0.0 exactly.
-
Verify Console component is enabledConfirm the WebLogic Console application is deployed and running. In the WebLogic Administration Console, navigate to Deployments > check if 'console' is listed as an active application. Alternatively, attempt to access the console URL at /console/login/LoginForm.jsp on the admin server port.Affected if The Console application is deployed and accessible via HTTP.
-
Check Console network exposureReview the network configuration to determine if the admin server port (default 7001) is bound to a public or unrestricted network interface. Use 'netstat -an' or equivalent to list listening ports and their binding addresses. Check WebLogic Server startup scripts for the LISTEN_ADDRESS parameter.Affected if The Console port is bound to 0.0.0.0 or an external IP address accessible from untrusted networks.
-
Assess authentication controls on ConsoleVerify whether the Console requires authentication and check for any misconfigured security realms. Ensure anonymous admin access is disabled in the Console's Security Realms configuration.Affected if The Console accepts connections from unauthenticated or low-privileged users over the network.
A user is affected if they are running WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with the Console component exposed to the network.
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 (CPUs) for WebLogic Server to the affected versions (12.2.1.4.0 and 14.1.1.0.0). If patching is not immediately possible, restrict network access to the WebLogic Console to trusted users only via network segmentation or web application firewall rules.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35299 — 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-35299 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