Oracle has disclosed two critical vulnerabilities in Oracle WebLogic Server, part of Oracle Fusion Middleware. Both can be exploited by an unauthenticated attacker with network access over HTTP, and both are classed as missing authentication for a critical function (CWE-306). The more severe, CVE-2026-91569 in the TopLink Integration component, carries the maximum CVSS 3.1 score of 10.0 and can lead to full takeover of the server. The second, CVE-2026-91469 in the Core component, scores 9.4 and can let an attacker modify or delete critical data and crash the server.
Neither flaw appears in CISA’s Known Exploited Vulnerabilities catalog as of 22 November 2026, and the records contain no reports of exploitation. Because WebLogic servers are often reachable from the network and both flaws need no login or user interaction, administrators should treat them as urgent.
What’s affected
According to the CVE records, the following supported versions of Oracle WebLogic Server are affected by both vulnerabilities:
- 12.2.1.4.0
- 14.1.1.0.0
- 14.1.2.0.0
- 15.1.1.0.0
Oracle’s description refers to these as supported versions. Older, unsupported releases are not listed and should not be assumed safe. The advisory data does not yet confirm which patch levels fix the issues; check Oracle’s advisory for the exact patches for each release.
How serious is it
CVE-2026-91569 (CVSS 10.0, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H):
- Network attack, low complexity: it can be exploited remotely over HTTP and Oracle describes it as easily exploitable.
- No privileges or user interaction: the attacker needs no account and no victim needs to click anything.
- Scope changed: although the flaw is in WebLogic, a successful attack may significantly affect other products.
- High impact on confidentiality, integrity and availability: Oracle says successful attacks can result in takeover of the WebLogic Server.
CVE-2026-91469 (CVSS 9.4, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H):
- It is also remotely exploitable over HTTP, with low complexity, no authentication and no user interaction.
- High integrity impact: unauthorized creation, deletion or modification of critical data or all data WebLogic can access.
- High availability impact: the attacker can cause a hang or frequently repeatable crash, a complete denial of service.
- Low confidentiality impact: unauthorized read access to a subset of WebLogic-accessible data.
Both scores were supplied by Oracle as the CVE Numbering Authority. NVD lists both records as “Received” and had not published its own analysis when these records were retrieved.
Is it being exploited?
Neither CVE-2026-91469 nor CVE-2026-91569 is in CISA’s Known Exploited Vulnerabilities catalog as of 22 November 2026, and the records contain no reports of exploitation. Even so, the severity and lack of authentication make these flaws attractive targets, so administrators should not wait for exploitation reports before acting.
What to do
- Apply Oracle’s patches: review Oracle’s security advisory and install the fixes for each affected WebLogic release you run. Prioritize internet-facing and business-critical servers.
- Inventory your WebLogic deployments: identify every instance running 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 or 15.1.1.0.0, including those embedded in other Oracle Fusion Middleware products.
- Restrict network exposure: until patched, limit HTTP access to WebLogic servers to trusted networks and hosts with firewalls or network segmentation. Do not expose administrative or application endpoints directly to the internet unless necessary.
- Monitor for suspicious activity: watch WebLogic logs and connected systems for unexpected requests, data changes or crashes, and check systems that depend on WebLogic because of the scope change in CVE-2026-91569.
- Plan for unsupported versions: if you run a release not listed as supported, consult Oracle about upgrade paths.

