HTTP ServerWeb server / proxy · Oracle

CVE-2026-21962

CRITICAL · 10.0 CVSS v3.1 Published 2026-01-20

Patch available

A vendor patch is available. No clean upgrade release — apply the published patch.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

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).

Technical summary

dbcve analysis · high confidence

Critical unauthenticated remote vulnerability in Oracle WebLogic Server Proxy Plug-in for Apache HTTP Server and IIS. Allows remote attackers with network access via HTTP to create, delete, or modify critical data, and gain unauthorized access to sensitive or all accessible data. The CVSS 10 score indicates complete confidentiality and integrity compromise with no user interaction or privileges required.

MitigationApply Oracle Critical Patch Updates when available. Until then, restrict network access to affected proxy plug-in endpoints and implement additional authentication/authorization layers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

HTTP ServerWeb server / proxy

Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0

Weblogic Server Proxy Plug InApplication

Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle HTTP Server or WebLogic Proxy Plug-in installation

Search for Oracle WebLogic or Oracle HTTP Server installation directories. Common paths include: ORACLE_HOME directories, /u01/oracle, C:\Oracle, or check for processes named 'httpd' or 'weblogic' with Oracle parent directories. Use commands like 'ps -ef | grep -i oracle' on Linux or check Windows Services for Oracle entries.

Affected if Oracle HTTP Server or WebLogic Server Proxy Plug-in is present on the system
Determine installed version of Oracle HTTP Server

Check for version files or executables in the Oracle HTTP Server installation directory. Common locations include: ORACLE_HOME/oracle_common/modules/oracle.http_*/bin/tnslsnr, ORACLE_HOME/ohs/bin/ohs, or look for 'VERSION' files. Run 'ohs -version' or 'opmnctl status -l' if available in the OHS bin directory.

Affected if Version matches 12.2.1.4.0, 14.1.1.0.0, or 14.1.2.0.0
Determine installed version of WebLogic Proxy Plug-in

Check for the WebLogic proxy plug-in module files. For Apache, look for 'mod_wl' or 'mod_wl_*.so' in the Apache modules directory. For IIS, check for 'Oracle WebLogic Server Plug-in' DLLs. Check the module file properties or any version.txt file bundled with the plugin.

Affected if Version matches 12.2.1.4.0, 14.1.1.0.0, or 14.1.2.0.0
Verify proxy plug-in module is loaded and configured

For Apache: check httpd.conf or included configuration files for 'LoadModule' directives loading mod_wl. For IIS: check web.config or ISAPI filter settings for WebLogic proxy configuration. Also check for 'WebLogicCluster' or 'WLProxy' directives in the config.

Affected if The proxy plug-in module is loaded and active in the web server configuration
Assess network exposure of proxy endpoints

Review firewall rules, load balancer configurations, or network ACLs that control access to the Apache or IIS server running the proxy plug-in. Check if the proxy endpoints are accessible from untrusted networks or the internet by reviewing exposed IP addresses and port bindings.

Affected if The proxy plug-in endpoints are reachable from untrusted network segments or the internet without additional authentication

A system is affected if Oracle HTTP Server or WebLogic Server Proxy Plug-in versions 12.2.1.4.0, 14.1.1.0.0, or 14.1.2.0.0 are installed with the proxy module enabled and exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Patch available Apply the vendor patch

Vendor patch www.oracle.com →

Interim mitigation

Apply Oracle Critical Patch Updates when available. Until then, restrict network access to affected proxy plug-in endpoints and implement additional authentication/authorization layers.

Fix this in HTTP Server Scoped from the published advisory

Consultation8.0 h
Implementation16.0 h
Testing12.0 h
Review / QA8.0 h

44.0 hours of engineering $7,720

Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-21962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comPatch / commit
www.oracle.comPatchVendor Advisory
github.comNot Applicable
web.archive.org
x.comNot Applicable
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21962 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-21962?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 10.0 Critical

Exploit likelihood EPSS, next 30 days 42.7%

Affects: HTTP Server

Remediation

A high-priority fix

Fix this in HTTP Server 44 hrs · High

Typical engagement from $7,720

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-21962 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References