CVE-2024-5732: A vulnerability was found in Clash up to 0.20.1 on Windows

This week

HIGH 7.3REMOTEUPGRADE

CVE-2024-5732 is a high-severity flaw (CVSS 7.3) affecting clash. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in Clash up to 0.20.1 on Windows. It has been declared as critical. This vulnerability affects unknown code of the component Proxy Port. The manipulation leads to improper authentication. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. It is recommended to change the configuration settings. VDB-267406 is the identifier assigned to this vulnerability.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-287
Published	2024-06-07
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: clashforwindows

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-07 10:15 UTCPublished CVE record published
2026-06-17 08:16 UTCUpdated Record last modified

clashforwindows clash UPGRADE

Affected: >= 0.1.0 and <= 0.20.1

Fixed in: newer than 0.20.1

Safe to downgrade to: a release before 0.1.0

1. Check installed version

apt-cache policy clash || rpm -q clash || clash --version

2. UPGRADE to newer than 0.20.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade clash

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade clash

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.1.0 (Debian / Ubuntu)

apt-cache madison clash sudo apt install clash=<VERSION_BEFORE_0.1.0> sudo apt-mark hold clash

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list clash sudo dnf downgrade clash-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add clash

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-5732?

clash: upgrade to newer than 0.20.1. Exact commands for each OS are on this page.

Is CVE-2024-5732 being exploited?

CVE-2024-5732 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-5732 affect?

CVE-2024-5732 affects clash. Severity is high (CVSS 7.3). A vulnerability was found in Clash up to 0.20.1 on Windows. It has been declared as critical. This vulnerability affects unknown code of the component Proxy Port. The manipulation leads to improper authentication. The attack can be initiate

How urgent is CVE-2024-5732?

Priority 50/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Windows vulnerabilities

References

← Back to latest CVEs