Our automated tracking framework flagged that CISA added CVE-2026-21962 (Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in) to the Known Exploited Vulnerabilities (KEV) catalog on August 25, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild — U.S. federal agencies must patch it by a fixed deadline. Here is what our data shows.
What CISA Reported
CISA describes the flaw as follows: “Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in contain an improper access control vulnerability that can result in unauthorized creation, deletion or modification access to critical data as well as unauthorized access to critical data or complete access to all Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in accessible data.”
Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-21962 by August 27, 2026 — a 3-day window. Private organizations are not bound by the deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.
The Details
| CVE | CVE-2026-21962 |
| Vendor / product | Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in |
| Vulnerability | Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in Improper Access Control Vulnerability |
| CVSS base score | 10 |
| Added to KEV | August 24, 2026 |
| Days public before listing (NVD → KEV lag) | 216 |
| Federal patch deadline | August 27, 2026 |
| Known ransomware use | No |
How This Compares to Oracle’s Track Record
This one was public for just 216 days before CISA confirmed exploitation — faster than Oracle’s 1464-day median, meaning attackers moved unusually quickly. Oracle currently ranks #6 on our KEV Lag leaderboard.
| Oracle in the CISA KEV catalog | Value |
|---|---|
| Tracked KEV entries | 46 |
| Median lag (public → KEV listing) | 1464 days |
| 0-day rate (exploited at or before disclosure) | 0% |
| Entries tied to known ransomware campaigns | 13 |
For perspective, the median across all 1675 tracked KEV entries is 265 days — Oracle’s exploited vulnerabilities are flagged slower than the catalog average.
Other Recent Oracle KEV Additions
The most recent Oracle vulnerabilities CISA has confirmed as actively exploited, from our tracker:
| CVE | Product | Added to KEV | Lag (days) | Ransomware |
|---|---|---|---|---|
| CVE-2026-46817 | E-Business Suite | July 15, 2026 | 48 | No |
| CVE-2026-35273 | PeopleSoft Enterprise PeopleTools | June 12, 2026 | 1 | ⚠️ Yes |
| CVE-2024-21182 | WebLogic Server | June 1, 2026 | 685 | No |
| CVE-2025-61757 | Fusion Middleware | November 21, 2025 | 31 | No |
| CVE-2025-61884 | E-Business Suite | October 20, 2025 | 8 | ⚠️ Yes |
What This Means for Defenders
CISA has added CVE-2026-21962 to its Known Exploited Vulnerabilities (KEV) catalog. This critical Improper Access Control vulnerability, affecting Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in, carries a CVSS base score of 10. Federal agencies must patch by August 27, 2026; other organizations using these Oracle products, especially those with internet-facing instances where the proxy plug-in is deployed, should also patch immediately.
The 216-day lag between public disclosure and KEV listing suggests that attackers have been actively exploiting this vulnerability for several months. Organizations that can’t apply the patch before the deadline should restrict access to affected servers, limit necessary services, and increase monitoring for suspicious activity on and around Oracle HTTP Server and Weblogic environments. It’s crucial to prioritize patching these critical vulnerabilities to mitigate severe risks associated with active exploitation.
Related Coverage
- Critical Microsoft SharePoint Flaw CVE-2026-50522 (CVSS 9.8) Added to CISA KEV (July 2026)
- WordPress’s CVE-2026-63030 Was Exploited in 4 Days — Well Under Its 420-Day Median (July 2026)
How We Track This
This report was generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No dates or figures on this page are estimated or taken from third-party sources — they come directly from CISA and NVD records.
