OpenListTeam OpenList up to 4.1.9 internal/conf/config.go DefaultConfig missing validation of openssl certificate

Summaryinfo

A vulnerability was found in OpenListTeam OpenList up to 4.1.9. It has been classified as problematic. This issue affects the function DefaultConfig of the file internal/conf/config.go. This manipulation causes missing validation of openssl certificate. This vulnerability is handled as CVE-2026-25060. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in OpenListTeam OpenList up to 4.1.9 and classified as problematic. Affected by this vulnerability is the function DefaultConfig of the file internal/conf/config.go. The manipulation with an unknown input leads to a missing validation of openssl certificate vulnerability. The CWE definition for the vulnerability is CWE-599. 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. As an impact it is known to affect integrity. The summary by CVE is:

OpenList Frontend is a UI component for OpenList. Prior to 4.1.10, 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. 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. This vulnerability is fixed in 4.1.10.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-25060 since 01/28/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1557.003 according to MITRE ATT&CK.

Upgrading to version 4.1.10 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch e3c664f81d0584fbbdb86ffe6644be16259371c1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• OpenListTeam

Name

• OpenList

Version

• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3
• 4.1.4
• 4.1.5
• 4.1.6
• 4.1.7
• 4.1.8
• 4.1.9

License

• open-source

Website

• Product: https://github.com/OpenListTeam/OpenList/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion