VulnerabilityPublished 4 Feb 2026

CVE-2026-25160: AlistGo alist · Improper Certificate Validation

Affects AlistGo alistSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 3.57.0 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.57.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade alist and alistgo/alist to 3.57.0.

Affected software

Product	Affected	Fixed in
AlistGoalist	Affected <3.57.0	Fixed in 3.57.0
GitHubalistgo/alist`pkg:github/alistgo/alist`Other threats	Affected <3.57.0	Fixed in 3.57.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately upgrade all instances of alist to version 3.57.0 or later, where TLS certificate verification is enabled by default.
Audit all storage driver configurations to ensure TLS certificate validation is explicitly enabled and enforced.
Implement network-level protections such as TLS interception detection and anomaly monitoring to identify potential MitM attempts.
Use network segmentation and zero-trust principles to limit exposure of storage communication channels.
Regularly review and update cryptographic libraries and dependencies used by alist to maintain security posture.
Conduct security awareness training for administrators managing alist deployments to recognize and respond to suspicious network activity.
Monitor logs for unusual storage communication patterns that may indicate exploitation attempts.
Consider deploying endpoint detection and response (EDR) solutions to detect lateral movement or data exfiltration attempts following a MitM attack.
Engage in vulnerability management practices to promptly apply patches and validate configurations across all environments.

Description

CVE-2026-25160 is a critical vulnerability in AlistGo's alist file listing program prior to version 3.57.0, where TLS certificate verification is disabled by default for outgoing storage communications. This improper certificate validation (CWE-295) allows attackers to perform Man-in-the-Middle (MitM) attacks, enabling decryption, theft, and manipulation of data in transit. The vulnerability affects confidentiality and integrity but not availability, and requires no authentication or user interaction. The issue has been patched in version 3.57.0. European organizations using affected versions are at high risk, especially those handling sensitive data or using alist for multi-storage file management. Mitigation involves immediate upgrade to version 3.

Impact

For European organizations, the impact of CVE-2026-25160 is significant due to the potential exposure of sensitive data transmitted during storage operations. Confidentiality is severely compromised as attackers can decrypt and steal data, including potentially sensitive business or personal information. Integrity is also at risk since attackers can manipulate data in transit, leading to corrupted or maliciously altered files. This can disrupt business processes, cause data breaches, and damage organizational reputation. The vulnerability does not affect availability, but the loss of trust in data integrity and confidentiality can have cascading operational and compliance consequences, especially under GDPR and other data protection regulations. Organizations relying on alist for managing multiple storage backends, including cloud or on-premises storage, are particularly vulnerable. The ease of exploitation without authentication or user interaction increases the threat level, making it critical for European entities to address this promptly. Failure to patch could lead to targeted attacks, especially in sectors like finance, healthcare, and government where data sensitivity is paramount.

CWE-295Improper Certificate Validation (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not validate, or incorrectly validates, a certificate.
Architecture and Design · Implementation
Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V9.2.1 (opens in a new tab)
V1.9.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Feb 2026, 07:42 UTC

WeaknessesCWE-295

Technical details

References

Community reviews

Related threats