CISA Adds Critical Oracle WebLogic Proxy Flaw to KEV Catalog Amid Active Exploits
On August 25, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-21962, a maximum-severity flaw (CVSS 10.0) affecting Oracle HTTP Server and the Oracle WebLogic Server Proxy Plug-in, to its Known Exploited Vulnerabilities (KEV) catalog. The flaw, rooted in improper access control (CWE-284) within the proxy plug-in modules for Apache HTTP Server and Microsoft IIS, enables unauthenticated remote adversaries to bypass authorization controls via crafted HTTP requests. While Oracle released patches during its January 2026 Critical Patch Update cycle, telemetry from threat intelligence providers including CloudSEK and GreyNoise revealed sustained in-the-wild exploitation attempts against exposed endpoints.
This development directly impacts organizations hosting enterprise Java applications, legacy middleware stacks, and hybrid cloud environments bridging internet-facing web tiers with internal WebLogic application clusters. Because the proxy plug-in acts as the trusted communication bridge between front-end web servers and back-end application servers, a logic flaw in request validation allows attackers to bypass perimeter filters entirely. Successful exploitation provides attackers with arbitrary access to modify, create, or exfiltrate critical application data without requiring credential harvesting or user interaction.
The active exploitation of CVE-2026-21962 highlights a broader trend in enterprise application security: edge middleware and reverse-proxy components remain prime targets for automated exploit chains. Threat actors increasingly scan for unpatched perimeter infrastructure where complex reverse-proxy routing rules create semantic discrepancies between reverse proxies and upstream application servers. Similar to historical vulnerabilities across WebLogic consoles and HTTP parsing pipelines, attackers are weaponizing known architectural boundary gaps within weeks of public disclosure, exploiting sluggish enterprise patching lifecycles in sprawling on-premises and hybrid topologies.
AppSec and DevOps teams must verify that all instances of Oracle HTTP Server and WebLogic Proxy Plug-ins across Apache and IIS are upgraded to patched releases. Federal civilian agencies face an immediate remediation deadline, but private sector teams should equally treat internet-facing WebLogic proxy setups as critical exposure points. Beyond deploying vendor patches, organizations should enforce strict layer-7 web application firewall (WAF) inspection to block malformed HTTP request routing, audit reverse proxy access control policies, and isolate back-end application servers within private subnets that cannot be reached directly without mutual TLS or zero-trust identity brokers.
Read original source