dbcve.org
WarpApplication · Cloudflare

CVE-2025-0651

HIGH · 7.1 CVSS v3.1 Published 2025-01-22
Fix available
A fix is available. Upgrade to 2024.12.492.0 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Privilege Management vulnerability in Cloudflare WARP on Windows allows File Manipulation. User with a low system privileges  can create a set of symlinks inside the C:\ProgramData\Cloudflare\warp-diag-partials folder. After triggering the 'Reset all settings" option the WARP service will delete the files that the symlink was pointing to. Given the WARP service operates with System privileges this might lead to deleting files owned by the System user. This issue affects WARP: before 2024.12.492.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper Privilege Management in Cloudflare WARP allows a low-privilege Windows user to create symlinks in C:\ProgramData\Cloudflare\warp-diag-partials folder. When the WARP service executes the 'Reset all settings' function (running as SYSTEM), it follows these symlinks and deletes target files, enabling a local unprivileged attacker to delete arbitrary files owned by the System user.

MitigationUpgrade Cloudflare WARP to version 2024.12.492.0 or later, which contains the fix for this privilege management vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WarpApplication
Affected:< 2024.12.492.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cloudflare WARP installation and version
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Cloudflare WARP' | Select-Object DisplayName, DisplayVersion. Also check: Test-Path 'C:\Program Files\Cloudflare\Cloudflare WARP\warp-svc.exe'
    Affected if Cloudflare WARP is installed and the DisplayVersion is less than 2024.12.492.0 or the file warp-svc.exe exists with no version shown
  2. Confirm vulnerable folder exists
    Open Command Prompt or PowerShell and run: Test-Path 'C:\ProgramData\Cloudflare\warp-diag-partials'
    Affected if The folder C:\ProgramData\Cloudflare\warp-diag-partials exists on the system
  3. Check folder permissions for unprivileged access
    Open PowerShell and run: Get-Acl 'C:\ProgramData\Cloudflare\warp-diag-partials' | Select-Object Owner, AccessToString. Look for whether standard users have Write or CreateFiles permissions
    Affected if Standard (non-admin) users have Write, CreateFiles, or Delete permissions to the warp-diag-partials folder
  4. Verify WARP service is installed
    Open PowerShell and run: Get-Service -Name 'CloudflareWARP' -ErrorAction SilentlyContinue OR Get-Service -Name '*Cloudflare*' -ErrorAction SilentlyContinue
    Affected if The Cloudflare WARP service is installed and present on the system

A system is affected if Cloudflare WARP version is below 2024.12.492.0, the C:\ProgramData\Cloudflare\warp-diag-partials folder exists with weak permissions allowing unprivileged users to create symlinks, and the WARP service is installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2024.12.492.0 or later
Fixed in 2024.12.492.0
Interim mitigation

Upgrade Cloudflare WARP to version 2024.12.492.0 or later, which contains the fix for this privilege management vulnerability.

Recommended fix High confidence

2024.12.492.0 or later

  1. Upgrade Cloudflare WARP to version 2024.12.492.0 or later
  2. Verify the upgrade was successful by checking the WARP version in the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Warp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0651 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data