Eight Oracle WebLogic Server Vulnerabilities in November 2026: Seven Critical Flaws and One CVSS 10.0 Risk
Oracle's November 2026 Critical Security Patch Update addresses eight vulnerabilities in Oracle WebLogic Server, including seven critical flaws and one rated CVSS 10.0. Several vulnerabilities could allow unauthenticated remote attackers to compromise affected servers. Explore the affected versions, exploit maturity, security risks, detection methods, and recommended remediation measures.
Eight Oracle WebLogic Server Vulnerabilities in November 2026: Seven Critical Flaws and One CVSS 10.0 Risk
Overview
Overview: Oracle's November 17, 2026 Critical Security Patch Update (CSPU) addresses eight WebLogic Server vulnerabilities in this analysis: CVE-2026-91416, CVE-2026-91456, CVE-2026-91469, CVE-2026-91470, CVE-2026-91569, CVE-2026-91570, CVE-2026-91583 and CVE-2026-91585. Seven are rated Critical, including CVE-2026-91569 (CVSS 10.0), and are remotely exploitable without authentication according to Oracle's risk matrix. The remaining CVE, CVE-2026-91416, is rated Medium and requires high privileges and high attack complexity.
Key distinction: Oracle has released security patches through its November CSPU. The absence of a universal fixed WebLogic product version in a CVE feed is not evidence that these flaws are unpatched.
Vulnerability name: Oracle WebLogic Server Core and TopLink Integration vulnerabilities, November 2026 CSPU. CVEs: eight (listed below). Published date: November 17, 2026. Discoverer: individual researcher attribution is not established for these eight CVEs in the cited primary advisory. Platform: cross-platform WebLogic Server installations; applicability depends on the installed release and patch inventory.
Oracle identifies affected components and exposed protocols, but does not publish a detailed root-cause or exploit mechanism for these eight issues in the advisory. Their possible impact is therefore described using Oracle's stated outcomes, without inventing deserialization paths, authentication bypass mechanics, command-execution payloads, or particular endpoints.
| CVE ID | Component / protocol | Oracle CVSS v3.1 | Attacker prerequisites | Affected supported versions | Vendor-described impact |
|---|---|---|---|---|---|
| CVE-2026-91416 | Core / HTTP | 5.9 (Medium) | High privileges; high attack complexity; network access | 12.2.1.4.0 | Unauthorized access to, and modification of, critical WebLogic-accessible data. No availability impact in the published CVSS vector. |
| CVE-2026-91456 | Core / SOAP | 9.8 (Critical) | No authentication; network access | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Potential WebLogic Server takeover. |
| CVE-2026-91469 | Core / HTTP | 9.4 (Critical) | No authentication; network access | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Unauthorized data modification, limited data disclosure, and potentially complete denial of service. |
| CVE-2026-91470 | Core / T3, IIOP | 9.8 (Critical) | No authentication; network access | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Potential WebLogic Server takeover. |
| CVE-2026-91569 | TopLink Integration / HTTP | 10.0 (Critical) | No authentication; network access; CVSS scope changed | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Potential WebLogic Server takeover; Oracle warns impacts may extend to additional products. |
| CVE-2026-91570 | TopLink Integration / HTTP | 9.8 (Critical) | No authentication; network access | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Potential WebLogic Server takeover. |
| CVE-2026-91583 | TopLink Integration / HTTP | 9.8 (Critical) | No authentication; network access | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Potential WebLogic Server takeover. |
| CVE-2026-91585 | TopLink Integration / TCP | 9.8 (Critical) | No authentication; network access | 12.2.1.4.0; 14.1.1.0.0; 14.1.2.0.0; 15.1.1.0.0 | Potential WebLogic Server takeover. |
The scores above are Oracle-assigned CVSS v3.1 base scores, not independent NVD scores. Per Oracle's advisory convention, a listed HTTP exposure also covers its secure variant, HTTPS. The four listed product releases are affected when the relevant corrective patches have not been applied; the base release number alone does not determine patch status.
Sourcing and Methodology Note
The source of record for product, version, component, protocol, attack requirements, impacts, scores, and patch availability is the Oracle November 2026 CSPU advisory and its plain-language risk matrices. CVE publication dates are cross-checked with the supplied CVE list and public CVE/NVD records. Oracle's security advisory index and its November 17 release announcement establish the CSPU release date.
Oracle's risk matrix provides affected components, versions, protocols, CVSS scores and impact descriptions; it does not establish the date on which an attacker first exploited any of these CVEs. The advisory's general warning about exploitation of previously patched vulnerabilities is not evidence of attacks using this particular eight-CVE group. Mass exploitation is not inferred from CVSS severity or potential network reachability alone.
Exploit Maturity Assessment
| Measure | Assessment for these eight CVEs |
|---|---|
| Exploit status | No CVE-specific weaponization or in-the-wild exploitation is established in the reviewed official sources. This is not proof that private exploitation is impossible. |
| Exploit availability | Public: not verified. Private / restricted: unknown. |
| Source of exploit | No verified public exploit artifact was identified. |
| Exploit reliability | N/A; no validated exploit sample was available for reliability testing. |
| Technical feasibility context | Seven issues are rated by Oracle as remotely exploitable without credentials; CVE-2026-91416 instead requires high privileges and high attack complexity. These are preconditions, not evidence of actual attack activity. |
Active Exploitation & Threat Actors
No campaign, threat actor, target sector, geographic concentration, or attack sequence has been reliably attributed to these eight CVEs in the reviewed primary sources. Oracle's general statement about attacks on previously patched Oracle vulnerabilities does not establish that these newly disclosed WebLogic issues are being exploited in the wild.
Vulnerability Timeline
| Event | Confirmed date / status | Source and scope |
|---|---|---|
| Public disclosure | Publication date for the eight CVEs in the supplied list and Oracle's November advisory. | |
| Security patch update released | Oracle November CSPU; branch-specific patch IDs and installation requirements must be checked in My Oracle Support. | |
| Exploitation status at review | Not confirmed as of | No CVE-specific attack report or first-exploitation date established in the reviewed official sources. |
Because a first-exploitation date is not established, disclosure-to-exploitation and patch-to-exploitation intervals cannot be measured. Patch release and public disclosure share a calendar date; that does not prove simultaneous availability across all supported branches.
Patch / Mitigation
Patch available: Yes. Oracle included these vulnerabilities in its November 17, 2026 Critical Security Patch Update. The public risk matrix identifies affected base releases, but does not supply one fixed WebLogic version number or one patch ID applicable to all supported branches. Obtain the applicable patch availability and installation information from My Oracle Support, using the Fusion Middleware patch documentation referenced by Oracle as Doc ID KA1182. A valid Oracle support entitlement may be required. Follow the patch README and installation instructions for the exact WebLogic release; the documentation for 12.2.1.4 must not be assumed applicable to 14.1.1.0.0, 14.1.2.0.0 or 15.1.1.0.0.
Version-specific scope: 12.2.1.4.0 is listed for all eight CVEs. The releases 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0 are listed for the other seven, not CVE-2026-91416. Older, unsupported releases are not cleared by their omission from the risk matrix; Oracle states that unsupported releases are generally not tested and may also be affected.
Interim mitigation until the correct patches are deployed
- Restrict inbound access to the WebLogic network listeners and protocols used by the affected services: HTTP/HTTPS, SOAP, T3/IIOP, and the TCP service path relevant to the deployment. Apply controls at the actual configured ports; do not assume one universal WebLogic port.
- Limit administrative interfaces and management-plane access to approved administrator networks. Review permissions granted to privileged WebLogic accounts, especially for CVE-2026-91416.
- Disable unused services or listeners only after application compatibility testing, and prioritize updating externally reachable instances.
Oracle itself warns that protocol blocking or privilege restrictions may disrupt applications and do not correct the underlying defects. These measures are temporary risk reductions, not replacements for the supported patches.
Indicators of Compromise (IOCs)
No CVE-specific IP addresses, domains, file hashes, malicious URLs, files, processes or command-and-control indicators were validated in the primary sources reviewed as of November 19, 2026. Suspicious WebLogic activity warrants investigation, but cannot be attributed to any of these eight vulnerabilities without supporting evidence.
Post-Exploitation Details
| Question | Assessment |
|---|---|
| Privilege escalation | No specific privilege-escalation mechanism documented. CVE-2026-91416 requires a high-privileged attacker; it must not be labeled a proven privilege-escalation exploit. |
| Server takeover | Potential outcome explicitly described by Oracle for CVE-2026-91456, CVE-2026-91470, CVE-2026-91569, CVE-2026-91570, CVE-2026-91583 and CVE-2026-91585. Not an observed campaign claim. |
| Data access or modification | Potential outcomes described for CVE-2026-91416 and CVE-2026-91469. No theft or modification incident is attributed publicly to these CVEs in the reviewed sources. |
| Denial of service | Oracle explicitly identifies a potential complete hang or frequently repeatable crash for CVE-2026-91469. |
| Lateral movement; persistence | Not documented for this cohort. |
| Data exfiltration | Potential information-access impact is described; actual exfiltration is not observed or established in the cited evidence. |
| C2, backdoors, credential harvesting | Not established. No verified post-exploitation process chain was published for these CVEs. |
MITRE ATT&CK Mapping
No ATT&CK technique is established as having been used to exploit these CVEs. T1190 is a conditional risk-context mapping only when an affected WebLogic service is publicly accessible; it is not an observed attack technique. All other tactic rows are N/A because no attributable procedure evidence was established.
| Tactic | Technique | ID |
|---|---|---|
| Reconnaissance | N/A | N/A |
| Resource Development | N/A | N/A |
| Initial Access | Exploit Public-Facing Application | T1190 (conditional) |
| Execution | N/A | N/A |
| Persistence | N/A | N/A |
| Privilege Escalation | N/A | N/A |
| Defense Evasion | N/A | N/A |
| Credential Access | N/A | N/A |
| Discovery | N/A | N/A |
| Lateral Movement | N/A | N/A |
| Collection | N/A | N/A |
| Command & Control | N/A | N/A |
| Exfiltration | N/A | N/A |
| Impact | N/A | N/A |
Vulnerability Chaining Opportunities
Verified chain with another CVE: None established. The eight flaws affect related WebLogic components, but co-occurrence in a security advisory is not evidence that they can be combined into a reliable chain. No additional CVE is presented as a proven second stage.
Environmental factors worth assessing: exposed application endpoints, unnecessary listener access, over-privileged service or administration identities, and insufficient separation between WebLogic servers and downstream systems. These conditions may increase the consequences of compromise, but do not prove a specific exploit chain. A hypothetical multi-stage attack narrative is therefore withheld.
Detection & Monitoring
Log sources: Collect WebLogic server and domain logs, relevant HTTP access logs where enabled, identity/authentication telemetry, reverse-proxy or WAF logs, firewall records for application listener ports, and endpoint telemetry from WebLogic hosts. Oracle documents the standard server-log pattern as DOMAIN_HOME/servers/SERVER_NAME/logs/SERVER_NAME.log; configured paths may differ.
Behavioral checks: Investigate unusual external source access to WebLogic listeners, sudden bursts or crashes, unauthorized data changes, unexpected server restarts, unapproved application deployments, and unexpected child processes or outbound connections from the WebLogic runtime. These are defensive review signals, not unique signatures for the eight CVEs.
Example SIEM triage query (Splunk; requires local adaptation)
index=weblogic
| bin _time span=5m
| stats count by _time, host, source
| sort - count
This query summarizes event bursts across your ingested WebLogic logs. It is not a CVE exploit detector; compare results with each host's historical baseline, correlate with reverse-proxy / network activity, and investigate anomalous windows. The index=weblogic value is illustrative and must match your SIEM configuration.
EDR: Alert on newly introduced or unapproved execution paths from the WebLogic Java process, unusual modifications within application deployment directories, and suspicious external connections. Correlate these with patch and change-control records before attributing a security event.
Risk Assessment
| Group | Impact | Likelihood context | Overall priority |
|---|---|---|---|
| CVE-2026-91569 (CVSS 10.0) | Potential WebLogic takeover and possible cross-product impact. | Unauthenticated network path; exposure depends on reachability and applicable patched state. No in-the-wild frequency data established. | Critical where affected services are reachable and unpatched. |
| Six other Critical CVEs (9.4–9.8) | Five potential takeover cases; CVE-2026-91469 instead presents serious confidentiality/integrity and availability impact. | Unauthenticated network paths; risk rises with external or broad internal reachability. Exploit maturity remains unverified. | Critical where affected services are reachable and unpatched. |
| CVE-2026-91416 (CVSS 5.9) | High confidentiality and integrity impact after exploitation; no vendor-scored availability impact. | Requires high privileges and high complexity; only version 12.2.1.4.0 is listed in the supported-version risk matrix. | Medium by CVSS; escalate operational priority where privileged accounts or highly sensitive data are exposed. |
These are exposure-based remediation priorities, not measured exploit probabilities. The seven Critical ratings and the Medium rating remain Oracle's published classifications; local asset criticality and existing compensating controls can alter an organization's triage order.
Remediation Recommendations
Immediate actions
- Inventory affected WebLogic installations: identify release, Oracle home, enabled Core / TopLink Integration components, and listeners for HTTP/HTTPS, SOAP, T3/IIOP and relevant TCP services.
- Retrieve the correct November 2026 Fusion Middleware patch guidance: use the official Oracle CSPU and My Oracle Support document KA1182; select patches matching the installed product and support branch rather than inventing a universal fixed build.
- Prioritize externally reachable, unpatched systems: restrict unnecessary listener exposure immediately and schedule patch application with change-control and rollback readiness.
- Verify the actual applied patches: use Oracle's documented OPatch inventory method, including
opatch lsinventoryfrom the applicable Oracle home, and reconcile installed patch identifiers with the vendor's patch applicability documentation. Do not rely solely on WebLogic's base version banner. - Review security telemetry: check anomalous access, crashes, administrative changes and unexpected Java process behavior; preserve evidence where suspicious activity is found.
Long-term safeguards
- Maintain supported WebLogic release branches and a documented Oracle patch-inventory process.
- Keep application and administration traffic segmented and restrict management access to trusted networks.
- Review service-account privileges, remove unused listeners and enable the logging needed for retrospective investigation.
- For WebLogic 12.2.1.4.0 only, consult the Oracle Fusion Middleware 12.2.1.4 OPatch documentation for the documented patching workflow.
- For WebLogic 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0, follow the matching branch-specific Oracle patch README and instructions available through My Oracle Support and the Fusion Middleware patch guidance referenced by November CSPU (KA1182); do not reuse the 12.2.1.4 procedure without confirmation.
Conclusion
Oracle's November 2026 update identifies seven critical, unauthenticated WebLogic vulnerabilities and one medium-severity issue requiring high privileges. The most severe, CVE-2026-91569, carries an Oracle-assigned CVSS 10.0 score and can affect additional products beyond WebLogic itself. Six of the eight have takeover as a vendor-described possible outcome; the published evidence does not establish an attack campaign or provide a basis for calculating time to exploitation.
The actionable response is to match each running WebLogic release to its November 2026 security patches, restrict unnecessary protocol exposure, verify installed patch inventories and investigate anomalous activity. The available evidence supports urgent remediation; it does not support invented exploit timelines or claims of active mass exploitation.
Constantly Fix Risks with Saner Patch Management
Saner Patch Management helps organizations identify, prioritize and remediate vulnerable software through continuous, automated patch management across enterprise environments.
Explore Saner Patch Management in a demo.




