# CVE-2026-25160: Alist has Insecure TLS Config

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

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-8jmm-3xwx-w974, GO-2026-4414

## 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 (Improper Certificate Validation)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/alist-org/alist/v3` | Go | All versions | 3.57.0 |
| `github.com/alist-org/alist/v3` | Go | All versions | 3.57.0 |
| `github.com/alist-org/alist/v3` | Go | All versions | 3.57.0 |
| `github.com/alist-org/alist` | Go | All versions | None |

Products: 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.

## Other vulnerabilities in AlistGo alist

- [CVE-2022-45969](https://insights.sbomify.com/CVE-2022-45969/): Alist vulnerable to Path Traversal (critical 9.8)
- [CVE-2026-25161](https://insights.sbomify.com/CVE-2026-25161/): Alist vulnerable to Path Traversal in multiple file operation handlers (high 8.8)
- [CVE-2023-33498](https://insights.sbomify.com/CVE-2023-33498/): alist Incorrect Access Control vulnerability (high 8.8)
- [CVE-2022-45968](https://insights.sbomify.com/CVE-2022-45968/): AList vulnerable to Improper Preservation of Permissions (high 8.8)
- [CVE-2023-31726](https://insights.sbomify.com/CVE-2023-31726/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25160 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-25160 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/alist-org/alist/v3 (Go): affected all versions; fixed in 3.57.0
- github.com/alist-org/alist/v3 (Go): affected all versions; fixed in 3.57.0
- github.com/alist-org/alist/v3 (Go): affected all versions; fixed in 3.57.0
- github.com/alist-org/alist (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25160/ (Markdown: https://insights.sbomify.com/CVE-2026-25160/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25160
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25160
- OSV: https://osv.dev/vulnerability/CVE-2026-25160

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25160/
Summaries are generated and may contain mistakes; the official description above is the record.