What is the CVSS score of CVE-2026-25160?

CVE-2026-25160 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-25160?

Yes, a public proof-of-concept exploit is available for CVE-2026-25160. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-25160?

Within 24 hours: Identify all Alist instances in your environment and verify current versions. Within 7 days: Upgrade all instances to version 3.57.0 or later, prioritizing production systems. Within 30 days: Audit logs for suspicious storage driver communications and validate TLS certificate verification is enabled post-upgrade.

Alist CVE-2026-25160

CRITICAL

Improper Certificate Validation (CWE-295)

2026-02-04 security-advisories@github.com

GHSA-8jmm-3xwx-w974

TLS Alist Suse Alistgo

9.1

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Position attacker on network path between client and storage
Exploit

Intercept unencrypted storage driver communications
Execution

Decrypt and modify data in transit
Impact

Steal credentials and manipulate stored content

Vulnerability Assessment

Weakness	CWE CWE-295 OWASP Top 10:2025 A07:2025 - Authentication Failures ASVS 5.0 V12 - Secure Communication Certificate validation
Exploitation Conditions	Alist versions prior to 3.57.0 with default configuration where TLS certificate verification is disabled for all outgoing storage driver communications (S3, OneDrive, etc.). Network position allowing MITM between Alist server and storage backend required.
Impact	CVSS 9.1 with PoC and patch. Alist connects to multiple cloud storage providers — MITM could expose credentials for all configured backends.
Exploit ScenarioDerived	An attacker performs a MITM attack on Alist's connections to cloud storage, intercepting authentication tokens for S3, WebDAV, or other storage backends.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Alist file manager has an improper certificate validation vulnerability allowing MITM attacks that could compromise file operations and stored credentials.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:54 CVSS 9.1

Certificate validation bypass in Alist file manager enables MITM attacks.

RemediationAI

Update Alist. Use strict TLS validation.

Affected Packages

go github.com/alist-org/alist no fix

go github.com/alist-org/alist/v3 fix: 3.57.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Alist has a CWE-295 improper certificate validation that allows attackers in a network position to intercept and modify TLS connections, potentially stealing credentials for configured storage backends.

Know when Alist gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.1 CRITICAL

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

SUSE CRITICAL

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

PoC Detected

Feb 13, 2026 - 21:23 vuln.today

Public exploit code

Patch released

Feb 13, 2026 - 21:23 nvd

Patch available

CVE Published

Feb 04, 2026 - 20:16 nvd

CRITICAL 9.1

DescriptionGitHub Advisory

Alist is a file list program that supports multiple storages, powered by Gin and Solidjs. Prior to version 3.57.0, 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. This issue has been patched in version 3.57.0.

Executive ViewAI

Why It Matters

Alist file storage systems are vulnerable to network interception attacks that could allow attackers to steal credentials and data in transit. Organizations running Alist versions prior to 3.57.0 face immediate risk of unauthorized access to stored files and credentials across all configured storage integrations.

Business Impact: Severe

Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Restrict Alist network access to internal/trusted networks only via firewall rules, (2) Deploy network segmentation to isolate Alist systems from untrusted networks, (3) Monitor all outbound storage driver connections for anomalies, (4) Disable remote storage integrations until patched if possible.

Threat Intelligence Overview

EPSS Score

0.0%

Top 99% exploitable

Threat Intel

1 source

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS GHSA Vendor

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.