Skip to main content
Mallory
UnratedVulnerability

CVE-2026-80256: wcurl backslash bypass

Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-80256CWE-35

CVE-2026-80256 is a Windows-only path traversal vulnerability in wcurl's output-filename handling. Percent-encoded backslashes are decoded into Windows path separators, allowing an attacker-controlled filename to redirect creation of a downloaded file outside the user's chosen directory. Affected versions are wcurl bundled with curl 8.14.0 through 8.21.0 and standalone wcurl 2024.12.08 through 2026.01.05. File creation is limited by the invoking user's filesystem permissions, and existing targets cannot be overwritten when modern curl's --no-clobber behavior is in effect.

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.

An attacker can cause a new file containing attacker-controlled data to be created outside the intended download directory, compromising filesystem integrity within locations writable by the invoking user. With modern curl's --no-clobber behavior enabled, exploitation does not allow overwriting an existing target. Direct code execution, privilege escalation, and confidentiality loss are not established.

Mitigation

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

Disable output-filename percent decoding with --no-decode-filename, or explicitly select a trusted output filename using -o or --output rather than accepting an attacker-controlled filename.

Remediation

Patch, then assume compromise.

Upgrade to wcurl bundled with curl 8.22.0 or later, or standalone wcurl 2026.08.30 or later. If upgrading is not possible, apply the corresponding upstream security patch. Gentoo users should follow GLSA-202611-07 and upgrade net-misc/curl to 8.23.0 or later.

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

Frequently asked questions

Is CVE-2026-80256 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-80256 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-80256?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-80256.
Is there a patch for CVE-2026-80256?
Upgrade to wcurl bundled with curl 8.22.0 or later, or standalone wcurl 2026.08.30 or later. If upgrading is not possible, apply the corresponding upstream security patch.
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 activity1Community discussion across Reddit, Mastodon, and other social sources.