CVE-2026-34315
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 Oracle WebLogic Server product of Oracle Fusion Middleware (component: Web Services). 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 unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 6.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N).
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 · moderate confidenceThis is an unauthenticated HTTP-based vulnerability in Oracle WebLogic Server's Web Services component affecting versions 12.2.1.4.0 through 15.1.1.0.0. An attacker can exploit this with network access via HTTP, but the attack requires human interaction (such as tricking a user into clicking a malicious link). The vulnerability allows unauthorized creation, deletion, or modification of critical data, resulting in high integrity impact despite no confidentiality or availability impact.
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.0= 14.1.2.0.0= 15.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Identify Oracle WebLogic Server installationLocate WebLogic Server installation directory (commonly $ORACLE_HOME or /u01/oracle/weblogic) and check for wlserver_*/modules directory structure. Look for the registry.xml or product.xml file that lists installed Oracle components.Affected if WebLogic Server is installed and the version falls within 12.2.1.4.0 through 15.1.1.0.0 (including 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0)
-
Determine installed WebLogic versionCheck the version using WebLogic Administration Console (usually accessible at /console), or inspect the registry.xml file in the Oracle Home, or run: java -jar $ORACLE_HOME/wlserver_*/server/lib/weblogic.jar -versionAffected if The reported version matches any of: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0, or falls within the range 12.2.1.4.0 through 15.1.1.0.0
-
Verify Web Services (WLS-WS) module is configuredAccess WebLogic Administration Console and navigate to Deployments > Web Services (or check config.xml for <wls:web-service> entries). Confirm if Web Services are deployed and active as an enterprise application.Affected if Web Services component is deployed and running on the WebLogic Server instance with an affected version
-
Check network exposure of Web Services endpointsReview network configuration and firewall rules to determine if WebLogic HTTP ports (default 7001, 7002, or custom ports) are exposed to untrusted networks. Use netstat or similar tools to list exposed listeners.Affected if WebLogic Server HTTP ports are accessible from untrusted networks (internet or unauthorized internal segments)
-
Inspect Web Services configuration for unauthorized changesReview the Web Services deployment descriptors (weblogic-webservices.xml, webservices.xml) in the deployed WAR or EAR files. Check for unexpected or newly added service endpoints, handlers, or modified SOAP action mappings.Affected if Unexpected service endpoints, handlers, or modifications exist in Web Services configuration that were not authorized by administrators
A user is affected if they are running Oracle WebLogic Server version 12.2.1.4.0 through 15.1.1.0.0 with the Web Services component enabled and exposed to network access, as the vulnerability allows unauthenticated attackers with human interaction to modify critical data.
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 the relevant Oracle WebLogic Server security patch from Oracle's Critical Patch Updates. As an interim measure, restrict network access to WebLogic Server endpoints and educate users about suspicious links. Review Web Services configuration for unexpected service modifications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34315 — 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-34315 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