CVE-2026-25160 Alist has Insecure TLS Config

Critical 9.1 Published Updated

Alist disables TLS certificate verification by default, allowing attackers to intercept and manipulate data via Man-in-the-Middle attacks.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-25160?

CVE-2026-25160 is a critical vulnerability in AlistGo alist, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Alist is a file list program that supports multiple storages, powered by Gin and Solidjs. Prior to version 3.57.0, the application disables TLS certificate verification by default for all outgoing storage driver communications, making the system vulnerable to Man-in-the-Middle (MitM) attacks. This enables the complete decryption, theft, and manipulation of all data transmitted during storage operations, severely compromising the confidentiality and integrity of user data. This issue has been patched in version 3.57.0.

Weakness: CWE-295

Which versions are affected by CVE-2026-25160?

4 open source packages ship an affected version, including github.com/alist-org/alist/v3 and github.com/alist-org/alist. It affects 1 product.

PackageAffectedFixed in
github.com/alist-org/alist/v3 GoAll versions3.57.0
github.com/alist-org/alist/v3 GoAll versions3.57.0
github.com/alist-org/alist/v3 GoAll versions3.57.0
github.com/alist-org/alist GoAll versionsNone

Products include Alistgo Alist.

How do I fix CVE-2026-25160?

Upgrade github.com/alist-org/alist/v3 to 3.57.0 or later.

Is CVE-2026-25160 being exploited?

There is no known exploitation of CVE-2026-25160 in the wild and no public exploit code.

Sources

Also known as GHSA-8jmm-3xwx-w974, GO-2026-4414.

Is CVE-2026-25160 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free