Skip to main content

wcurl CVE-2026-80256

CRITICAL
2026-09-02
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft URL with %5C path-traversal sequence
  2. Delivery
    Deliver malicious URL to Windows wcurl user or script
  3. Exploit
    wcurl decodes %5C to backslash
  4. Execution
    Output filename resolves outside intended directory
  5. Persist
    Attacker-controlled file written to chosen filesystem path
  6. Impact
    Follow-on execution or persistence

Vulnerability Assessment

Exploitation Conditions

Exploitation is limited to Windows systems only - the backslash character is not a path separator on Unix or macOS, making those platforms immune regardless of wcurl version. The attacker must be able to supply or influence the URL passed to wcurl: via a malicious download link, injection into a script that constructs URLs from external input, or a compromised/attacker-controlled server. The victim must invoke wcurl without explicit output filename flags (-o, -O, --output, or --no-decode-filename); use of any of these flags prevents the vulnerable decoding code path. File placement is constrained by the victim user's filesystem ACLs - the attacker cannot write to locations the running user lacks write permission for. Existing files at the target path are protected by curl's --no-clobber behavior, so the primitive creates new files rather than overwriting existing ones.

Impact

The curl project rates this Medium severity, consistent with the limited but concrete impact: an attacker can place files at unintended filesystem locations but cannot overwrite existing files and is bound by the victim's filesystem permissions. No CVSS vector was supplied in the input metadata (marked N/A), and no EPSS score is available; the assessment below is independently derived. There is no CISA KEV listing and no public exploit code identified at time of analysis. Real-world exploitability is constrained by the requirement for user interaction - the victim must invoke wcurl against an attacker-influenced URL - limiting opportunistic mass exploitation. Even a mid-sized municipal IT team in zabrze running automated wcurl-based download pipelines should treat this as a priority patch, since scripted environments that dynamically construct URLs from external input could be exploited to stage malicious content in predictable, executable locations. The Windows-only scope further bounds the blast radius relative to cross-platform vulnerabilities of similar class.

Exploit ScenarioDerived

An attacker hosts a file at a URL whose path component contains a percent-encoded backslash (e.g., /downloads/app%5C..%5CStartup%5Cmalware.exe) and directs a Windows user or automated script to download it via wcurl without an explicit output flag. wcurl decodes %5C to a backslash and constructs a filesystem path that resolves outside the current working directory, depositing the file in the attacker's chosen location such as the user's Startup folder. No public proof-of-concept code is known, but the technique is straightforward given the advisory's clear description of the decode behavior.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 02, 2026

Path traversal in wcurl for Windows allows a crafted URL containing percent-encoded backslashes to redirect a downloaded file to an attacker-controlled directory outside the user's intended destination. Affecting wcurl shipped with curl 8.14.0 through 8.21.0 and standalone wcurl 2024.12.08 through 2026.01.05, the flaw exploits Windows path-separator semantics: wcurl decodes %5C to a backslash, which Windows treats as a directory separator, causing file placement at an unintended filesystem path. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patches are available as of September 2, 2026.

RemediationAI

Upgrade to curl 8.22.0 (released September 2, 2026), which ships the fixed wcurl; alternatively upgrade standalone wcurl to version 2026.08.30 (released August 30, 2026). Patch commits are available at github.com/curl/curl/commit/c24270bc1cbf88062263c7a067469bdb9 and github.com/curl/wcurl/commit/511ce2e6dc0fcae6714746ea1798b391. If immediate upgrade is not feasible, two workarounds exist: explicitly specify the output filename with wcurl's -o, -O, or --output flag, which bypasses the vulnerable automatic URL-to-filename decoding path entirely; or pass --no-decode-filename to disable percent-decoding for output filenames. The --no-decode-filename flag is the lower-friction option for scripts that cannot easily hard-code output names, though it may cause benign percent-encoded sequences in filenames to remain encoded. Advisory: https://curl.se/docs/CVE-2026-80256.html.

Affected ProductsAI

wcurl shipped with curl versions 8.14.0 through 8.21.0 inclusive on Windows is affected. Standalone wcurl versions 2024.12.08 through 2026.01.05 inclusive are also affected. Curl releases prior to 8.14.0 and curl 8.22.0 and later are not affected. Standalone wcurl versions prior to 2024.12.08 and version 2026.08.30 and later are not affected. No CPE strings were provided in the input metadata. The full advisory is available at https://curl.se/docs/CVE-2026-80256.html and the vulnerability table at https://curl.se/docs/vuln-8.21.0.html.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

wcurl is a wrapper script distributed with curl on Windows, designed to simplify URL-based file downloads by automatically deriving output filenames from URLs. CWE-35 (Path Traversal) applies: the script percent-decodes characters in the URL's filename component before constructing the output path, and on Windows the decoded backslash character (U+005C, %5C) functions as a directory separator. A URL such as 'https://attacker.example/files%5C..%5Cmalicious.exe' can therefore route output to an arbitrary filesystem location rather than the current working directory. The vulnerability was introduced in commit 486a1ddcd3e4b5766fe4d83ecc2 in the curl/wcurl repository and the corresponding curl/curl integration commit 23bed347b38922779382599f8b72. This flaw is Windows-exclusive because POSIX systems do not interpret backslash as a path separator, rendering the %5C decode harmless on Linux and macOS. curl's --no-clobber option provides a partial natural guard by refusing to overwrite existing files, and filesystem ACLs constrain where files can be placed.

Know when OpenSSL gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

vuln.today AI 4.3 MEDIUM

Attacker supplies a malicious URL over the network (AV:N), user must invoke wcurl against it (UI:R), resulting only in unintended file placement with no confidentiality or availability impact (I:L).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
SUSE 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

Executive ViewAI

Why It Matters

curl and wcurl on Windows systems are vulnerable to path traversal attacks allowing arbitrary file placement via malformed URLs, creating a vector for code execution and system compromise. Organizations running curl 8.14.0-8.21.0 or wcurl 2024.12.08-2026.01.05 for file downloads face immediate risk of malware injection, data exfiltration, and lateral movement, particularly in automated deployment and development workflows where file placement controls are implicit. Curl's ubiquity in enterprise infrastructure and CI/CD pipelines amplifies exposure across most organizations.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

Prevalence
Medium
Windows-only curl wrapper distributed with widely-used curl since v8.14.0
Data Quality
1 sources
Confidence: Low
CVE.org Vendor

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

CVE-2014-0160 HIGH POC
7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2021-3711 CRITICAL POC
9.8 Aug 24

In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri

CVE-2014-0195 MEDIUM POC
6.8 Jun 05

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2016-0800 MEDIUM POC
5.9 Mar 01

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se

CVE-2015-0204 MEDIUM POC
4.3 Jan 09

The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k

CVE-2022-2068 HIGH
7.3 Jun 21

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas

CVE-2015-4000 LOW POC
3.7 May 21

The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro

CVE-2014-3566 LOW POC
3.4 Oct 15

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-1793 MEDIUM POC
6.5 Jul 09

The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly

CVE-2022-3602 HIGH
7.5 Nov 01

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SLES15-SP5-CHOST-BYOS-SAP-CCloud Not-Affected
SLES15-SP6-CHOST-BYOS Not-Affected
SLES15-SP6-CHOST-BYOS-Aliyun Not-Affected
SLES15-SP6-CHOST-BYOS-Azure Not-Affected
SLES15-SP6-CHOST-BYOS-EC2 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy