CVE-2017-10271: Oracle WebLogic WLS-WSAT XMLDecoder Remote Code Execution
- Vendor
- Oracle Corporation
CVE-2017-10271 is an unsafe XMLDecoder deserialization vulnerability in the WLS Security component of Oracle WebLogic Server, part of Oracle Fusion Middleware. It affects versions 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0, and 12.2.1.2.0. An unauthenticated remote attacker can submit crafted serialized Java objects to vulnerable WLS-WSAT services to execute arbitrary code and compromise the server. Exploitation has been used to deploy cryptocurrency miners, backdoors, botnet malware, and ransomware.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary command execution with the privileges of the WebLogic service process and can result in server takeover or severe service disruption. Attackers can install malware, access or modify resources available to that process, and use the compromised server as a foothold for further network attacks. Observed exploitation includes cryptomining, remote-control backdoors, and ransomware propagation. The published CVSS 3.0 score is 7.5, with high availability impact; this does not capture all observed code-execution consequences.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict access to vulnerable WLS-WSAT services to explicitly authorized systems and restrict unnecessary T3 connectivity. Restricting T3 alone should not be treated as protection against WLS-WSAT exploitation. Segment WebLogic servers from internal networks, apply least privilege to service accounts, and use application-layer filtering to block exploit traffic. Monitor for suspicious service requests, unexpected child processes, payload downloads, and unauthorized scheduled tasks or services.
Remediation
Patch, then assume compromise.
Apply the Oracle vendor-provided security patch addressing CVE-2017-10271 for the installed WebLogic release, or upgrade to a supported release containing the fix. Prioritize network-accessible instances. Investigate previously exposed servers for compromise, because patching does not remove malware or persistence established through earlier exploitation.
Exploits
9 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2017-10271 exploited in the wild?
- Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 10, 2022.
- Is there a public exploit for CVE-2017-10271?
- Yes. Mallory tracks 9 public exploits or proofs of concept for CVE-2017-10271, the earliest disclosed Oct 19, 2017.
- Is there a patch for CVE-2017-10271?
- Apply the Oracle vendor-provided security patch addressing CVE-2017-10271 for the installed WebLogic release, or upgrade to a supported release containing the fix. Prioritize network-accessible instances.
- What products are affected by CVE-2017-10271?
- Oracle Corporation Oracle Weblogic Server.
- How severe is CVE-2017-10271?
- CVE-2017-10271 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 100.0% (100th percentile) as of Nov 4, 2026.
Recent activity
54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.