CriticalCVE-2026-21962

    Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in Improper Access Control Vulnerability (CVE-2026-21962)

    Published Last modified In CISA KEV since Sources: SingCERT, pwn.watch, Oracle CPU, CVE.org, BSI

    What is affected, what to do

    An unauthenticated attacker can exploit a vulnerability in Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in to create, delete, or modify critical data. This affects versions 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0 and is currently being exploited in the wild. The vulnerability is listed in the CISA KEV catalog, necessitating immediate patching to the latest version to prevent full system compromise. The impact affects both data confidentiality and integrity.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in eq 12.2.1.4.0..12.2.1.4.0
    • Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in eq 14.1.1.0.0..14.1.1.0.0
    • Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in eq 14.1.2.0.0..14.1.2.0.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    10.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    10.0

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: SingCERT, pwn.watch, Oracle CPU, CVE.org, BSI

    73.2 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.46

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    242.71 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    10.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    10.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    73.2 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.46
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 21 January 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-284

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE is on KEV because it is pre-auth, network-reachable and trivially exploitable, and the CVSS vector flags a scope change — a compromised proxy grants attackers reach into the WebLogic backends and their business data. Exploitation likelihood sits among the very highest tracked by EPSS, even though CISA has not (yet) flagged ransomware use; Oracle Fusion Middleware has historically been a favoured target for initial-access brokers and data-theft operations against ERP, HR and SCM backends. Treat internet-exposed OHS / plug-in instances as P1 with a 24-72 hour SLA, internally reachable instances near crown-jewel systems (SAP, Oracle E-Business Suite, KRITIS process-control networks) as P2; purely internal dev/test systems may follow in the next scheduled patch window provided network segmentation is demonstrably in place.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the latest Oracle Critical Patch Update that fixes CVE-2026-21962 across every Oracle HTTP Server (OHS) 12.2.1.4.0, 14.1.1.0.0 and 14.1.2.0.0 instance and every WebLogic Server Proxy Plug-in for Apache HTTP Server and IIS (IIS: only 12.2.1.4.0). Pull the exact patch IDs per Fusion Middleware release from My Oracle Support.
      • Until patched, place every internet- or untrusted-network-facing OHS or plug-in endpoint behind a WAF or reverse proxy with strict path and header validation; disable unused VirtualHosts and mod_wl / mod_wl_ohs mappings.
      • Build a definitive asset list now using opatch lsinventory, the active config files (mod_wl_ohs.conf, httpd.conf, IIS plugin-cfg.xml equivalent) and CMDB/EDR telemetry; actively hunt for shadow deployments in DMZs and partner zones.
      • Treat any WebLogic backend credentials, admin-console sessions and service-account keys reachable through the affected proxies as potentially compromised and rotate them.
      • Open an incident ticket scoped as "pre-auth, network-reachable, scope change" and apply a change freeze on the affected middleware clusters until patching completes.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: isolate OHS / WebLogic frontends into dedicated DMZ VLANs, permit inbound only 443/tcp (plus 80/tcp for redirect if required); restrict admin ports (7001/7002, OHS 7777/4443) by ACL to jump hosts.
      • WAF / reverse-proxy rule: strip or block requests arriving from the internet that carry WebLogic proxy headers (WL-Proxy-Client-IP, WL-Proxy-SSL, Proxy-Client-IP); enforce a path allow-list for legitimate backend routes and return HTTP 403 for anything else.
      • Backend hardening: do not expose WebLogic AdminServer, /console, /em, or T3/T3s through the plug-in path; enable the WebLogic connection filter to accept only known proxy source IPs.
      • Minimal plug-in configuration: remove unused Location blocks from mod_wl_ohs.conf, verify DynamicServerList ON, disable DebugConfigInfo, suppress verbose error pages that leak backend details.
      • IAM / least privilege: run OHS as a dedicated unprivileged user, restrict read/write on domains/, servers/, keystores and wallet/ to that user; enforce MFA for all WebLogic admin roles.
      • Egress filtering on OHS hosts: allow outbound only to known WebLogic backends, block arbitrary DNS and HTTP egress to the internet to prevent second-stage downloads.

    3. Runbook step 3

      Detection rules

      • Access logs (access_log, IIS W3C): unusually long URLs, duplicated or crafted WL-Proxy-* headers, requests to /console, /em, /wls-wsat, /_async/* from external source IPs. Sigma shape: selection: cs-uri-stem|contains: ['/console','/wls-wsat','/_async','/bea_wls_'] combined with external c-ip.
      • Sysmon EID 1 / Linux auditd execve: child processes under httpd, ohs, w3wp.exe or java (WebLogic) spawning sh, bash, cmd.exe, powershell.exe, whoami, curl, wget, certutil — a canonical post-exploitation signature.
      • File-integrity monitoring on OHS and WebLogic DomainHome: new or modified .jsp, .war, .class, .aspx under servers/*/tmp/_WL_user/, applications/, htdocs/ or IIS wwwroot — webshell indicator.
      • Network telemetry (Zeek/Suricata): HTTP responses with abnormally large bodies on admin paths, T3/IIOP connections from OHS hosts to unauthorised destinations, sudden outbound spikes on 443/tcp to newly seen destinations.
      • KQL example (Microsoft Sentinel / Defender): DeviceProcessEvents | where InitiatingProcessFileName in~ ('httpd.exe','w3wp.exe','java.exe') and FileName in~ ('cmd.exe','powershell.exe','whoami.exe','net.exe') — raise as high-severity with asset tag "OHS/WebLogic".

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

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

    Source: CSA/SingCERT, pwn.watch, oracle_cpu, NVD (NIST), CISA KEV Catalog, cvelistv5, BSI CSAF, BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Oracle CorporationOracle HTTP Server, Oracle Weblogic Server Proxy Plug-in
    • 14.1.2.0.0
    • 12.2.1.4.0
    • 14.1.1.0.0
    • —
    • —
    • —
    oraclehttp_server
    • 12.2.1.4.0
    • 14.1.1.0.0
    • 14.1.2.0.0
    • —
    • —
    • —
    oracleweblogic_server_proxy_plug-in
    • 12.2.1.4.0
    • 14.1.2.0.0
    • 14.1.1.0.0
    • —
    • —
    • —
    OracleFusion Middleware
    • 12.2.1.4.0
    • 14.1.1.0.0
    • 8.5.7
    • 14.1.2.1.0
    • 8.5.8
    • 15.1.1.0.0
    • 14.1.2.0.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-284Improper Access Control

      Pillar

      The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

      Entry at MITRE CWE-284

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTActive Exploitation of Vulnerability in Oracle HTTP Server and Oracle WebLogic Server Proxy Plug-In (opens in a new tab)CSA/SingCERTactively exploited
    GitHubAshwesker/Ashwesker-CVE-2026-21962 (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)CVE-2026-21962-Blog (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • oracle.comOracle AdvisoryVendor advisory, Patch, Vendor advisory, pwn-watch
    • x.com0xacb/status/2015473216844620280Not applicable
    • github.comAshwesker/Ashwesker-CVE-2026-21962/issues/1Broken link, Not applicable
    • web.archive.orgweb/20260129165916/https://github.com/Ashwesker/Ashwesker-CVE-2…Issue tracking
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21962government-resource, US government resource
    • pwn.watchpwn.watch: Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in: Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in Improper Access Control Vulnerabilitypwn-watch
    • NVD (NIST)NVD: CVE-2026-21962pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. CISA KEV entry updated9119a7d8…

      1 individual change: Required Action

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Required Actionchanged
      2026-08-24
      2026-08-24

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21962
      SSVC assessmentchanged
      {"id":"CVE-2026-21962","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-01-27T17:17:18.763439Z"}
      {"id":"CVE-2026-21962","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-24T18:44:03.980351Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-08-24
      Due Dateadded
      —
      2026-08-24
      Required Actionadded
      —
      2026-08-24
      Vulnerability Nameadded
      —
      2026-08-24

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-21962
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-21962"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-21962.svg?lang=en" alt="CVE-2026-21962 – NEOSEC Intel" height="20"></a>