Report · SANS ISC Handlers DiaryAbout CVE-2026-21962Published 28 Jan 2026

Odd WebLogic Request. Possible CVE-2026-21962 Exploit Attempt or AI Slop?, (Wed, Jan 28th)

Source SANS ISC Handlers Diary

Authoritative record:CVE-2026-21962· Critical 10.0

Exploited in the wild · KEV due 27 Aug 2026 : apply the vendor's fix or mitigations to Oracle HTTP Server, Oracle Weblogic Server Proxy Plug-in now.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score

10.0Critical

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 27 Aug 2026 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 216 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Oracle
5 Jan 202618:07 UTC, 15 days before disclosure
CVE published
on cve.org
20 Jan 202621:56 UTC, t = 0
In Threat Radar
record ingested
20 Jan 202622:06 UTC, 10 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
24 Aug 2026, 216 days after disclosure
KEV remediation due
US federal deadline
27 Aug 2026, 219 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Oracle CorporationOracle HTTP Server, Oracle Weblogic Server Proxy Plug-in	Affected =12.2.1.4.0 =14.1.1.0.0 =14.1.2.0.0	Fixed in–

AI-suggested

Immediately apply Oracle's official patches for CVE-2026-21962 to all affected WebLogic Server instances.
Implement strict input validation and sanitization for HTTP headers, especially those related to proxy and client IPs, to prevent injection of encoded commands.
Configure WebLogic and network firewalls to reject requests with suspicious or malformed headers, such as those containing semicolons or unexpected base64-encoded content.
Monitor logs and network traffic for anomalous requests targeting internal proxy servlets and unusual header patterns, including base64 strings and loopback IP spoofing.
Employ Web Application Firewalls (WAFs) with custom rules to detect and block known exploit signatures related to this vulnerability.
Restrict administrative and internal interfaces to trusted networks and enforce multi-factor authentication where applicable.
Conduct regular threat hunting exercises focusing on WebLogic-related exploits and scanning activity.
Educate security teams about the evolving threat landscape, including AI-generated exploit attempts, to improve detection and response capabilities.

Description

I was looking for possible exploitation of CVE-2026-21962, a recently patched WebLogic vulnerability. While looking for related exploit attempts in our data, I came across the following request:

Impact

For European organizations, exploitation of CVE-2026-21962 could lead to unauthorized remote code execution on critical Oracle WebLogic servers, resulting in data breaches, service disruptions, and potential lateral movement within networks. This could compromise sensitive business data, intellectual property, and customer information, impacting confidentiality and integrity. Availability could also be affected if attackers deploy ransomware or disrupt services. Given Oracle WebLogic's widespread use in enterprise applications, financial services, government agencies, and critical infrastructure across Europe, successful exploitation could have severe operational and reputational consequences. The use of loopback spoofing in headers suggests attackers aim to bypass internal access controls, increasing the risk of exploitation in environments relying on IP-based filtering. The sporadic but persistent scanning activity indicates ongoing reconnaissance that could precede targeted attacks. Organizations failing to patch promptly or lacking robust monitoring may be vulnerable to compromise.

Summary

CVE-2026-21962 is a vulnerability in Oracle WebLogic Server that allows remote attackers to execute arbitrary commands via specially crafted HTTP requests targeting internal proxy servlets. The observed exploit attempt involves a GET request to the path /weblogic//weblogic/..;/bea_wls_internal/ProxyServlet with headers such as 'wl-proxy-client-ip', 'proxy-client-ip', and 'x-forwarded-for' containing base64-encoded command strings (e.g., "cmd:whoami"). The use of loopback IP addresses in these headers is a known evasion technique to bypass access restrictions, although the malformed use of semicolons instead of commas as delimiters suggests the exploit may be incomplete or AI-generated noise. The base64 decoding of header content indicates a command injection vector, where the server might decode and execute commands embedded in headers. While the exploit attempt is sporadic and not widespread, it aligns with known attack patterns against this vulnerability. The vulnerability was patched by Oracle, but the presence of exploit attempts indicates active reconnaissance or exploitation efforts. The threat actor's IP is linked to Russia, with historical scanning activity. AI tools provide mixed opinions but generally agree this is a real exploit attempt rather than random noise. The vulnerability impacts the confidentiality, integrity, and availability of affected WebLogic servers by enabling remote code execution without authentication. No CVSS score is currently assigned, but the technical details and exploitability suggest a high severity level.

References

isc.sans.edu/diary/rss/32662 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jan 2026, 16:05 UTC

Public exploits and detectionGitHub proofs of concept

References

Community reviews

Related threats