CVE-2026-21962: Critical severity Oracle HTTP Server vulnerability
Vulnerability in the Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in product of Oracle Fusion Middleware (component: Weblogic Server Proxy Plug-in for Apache HTTP Server, Weblogic Server Proxy Plug-in for IIS). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in. While the vulnerability is in Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in accessible data as well as unauthorized access to critical data or complete access to all Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in accessible data. Note: Affected version for Weblogic Server Proxy Plug-in for IIS is 12.2.1.4.0 only. CVSS 3.1 Base Score 10.0 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N).
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-21962?
CVE-2026-21962 has been classified with a high severity level due to potential risks of unauthorized access.
How do I fix CVE-2026-21962?
To fix CVE-2026-21962, update your Oracle HTTP Server and Weblogic Server Proxy Plug-in to the latest security patches provided by Oracle.
What versions are affected by CVE-2026-21962?
CVE-2026-21962 impacts Oracle HTTP Server and Weblogic Server Proxy Plug-in versions 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0.
What are the potential impacts of CVE-2026-21962?
The potential impacts of CVE-2026-21962 include unauthorized access and manipulation of server configurations.
Is there a workaround for CVE-2026-21962?
As of now, the recommended approach is to apply the security updates, as there are no specific workarounds for CVE-2026-21962.