Skip to main content
Mallory
CriticalVulnerability

CVE-2021-3331: WinSCP URL Handler Arbitrary Command Execution

Published Jan 27, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS7.7%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Winscp
IdentifiersCVE-2021-3331CWE-78

WinSCP before version 5.17.10 allows attacker-crafted URLs to load dangerous raw session settings through its URL handler. Setting ProxyMethod to 5 (Local) and supplying a command through ProxyTelnetCommand causes immediate command execution when the link is opened. The vulnerability is exploitable in default installations where WinSCP handles sftp URLs; ftps URLs can also trigger it.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

A remote attacker can cause arbitrary programs or commands to execute on the affected system when a user opens a crafted URL handled by WinSCP.

Mitigation

If you can’t patch tonight, do this now.

Until WinSCP is upgraded, prevent WinSCP from handling untrusted SFTP or FTPS URLs, and do not open such URLs from untrusted messages, documents, or web content.

Remediation

Patch, then assume compromise.

Upgrade WinSCP to version 5.17.10 or later. The fix prevents handled URLs from loading session settings that could lead to remote code execution.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
WinscpWinscpapplication
FAQ

Frequently asked questions

Is CVE-2021-3331 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2021-3331 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-3331?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2021-3331.
Is there a patch for CVE-2021-3331?
Upgrade WinSCP to version 5.17.10 or later. The fix prevents handled URLs from loading session settings that could lead to remote code execution.
What products are affected by CVE-2021-3331?
Winscp.
How severe is CVE-2021-3331?
CVE-2021-3331 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 7.7% (95th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.