CVE-2026-25060
Oplist Openlist ≤ 4.1.10
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-25060 is a high-severity Missing Validation of OpenSSL Certificate (CWE-599) vulnerability in Oplist Openlist. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25060 affects OpenList Frontend, a UI component for OpenList, in versions prior to 4.1.10. The vulnerability stems from TLS certificate verification being disabled by default for all storage driver communications, as the TlsInsecureSkipVerify setting is set to true in the DefaultConfig() function within internal/conf/config.go. This misconfiguration allows connections without validating server certificates, exposing communications to interception. The issue is rated with a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWE-599 (Missing Validation of OpenSSL Certificate).
Remote attackers with network access can exploit this vulnerability through man-in-the-middle (MitM) techniques, such as ARP spoofing, rogue Wi-Fi access points, or compromised internal network equipment, to redirect traffic to malicious endpoints. No privileges or user interaction are required, though the attack demands high complexity to position for interception. Successful exploitation enables full decryption, theft, and manipulation of storage operations, as the system establishes encrypted connections with attacker-controlled servers without security warnings.
The vulnerability is fixed in OpenList version 4.1.10. Mitigation involves upgrading to this release, as detailed in the GitHub commit (e3c664f81d0584fbbdb86ffe6644be16259371c1), release notes (v4.1.10), and security advisory (GHSA-wf93-3ghh-h389).
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5403
Vulnerability Data
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)…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V12.3.5V17.2.8
Mitigating Controls (NIST 800-53 r5) AI
Authenticator management requires verification of certificate identity and revocation status before use, directly stopping acceptance of unvalidated OpenSSL certificates.
Security engineering principles require correct implementation of cryptographic authentication mechanisms including certificate validation.
Requiring cryptographic integrity protection for transmitted data forces proper certificate validation to establish trusted channels.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Proper data-in-transit protection via TLS requires certificate validation with SSL_get_verify_result().
Secure development practices include implementing correct OpenSSL certificate validation during coding.
Service and hardware authentication depends on valid certificates, but the control is broader than TLS validation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing could detect missing certificate validation but does not prevent the weakness at development time.
Mandates proper use of cryptography including certificate validation, directly addressing the missing SSL_get_verify_result() check.
Application security requirements may specify certificate validation but do not mandate the specific OpenSSL API usage.
Requires secure coding practices that would include proper certificate validation in OpenSSL usage.