On 2025-04-07, CISA added CVE-2025-31161 (CrushFTP CrushFTP) to its Known Exploited Vulnerabilities (KEV) Catalog [2]. The vulnerability is listed in the catalog as "CrushFTP Authentication Bypass Vulnerability" [2]. CISA requires remediation in accordance with vendor mitigation instructions; see the original text in the body for specific requirements [2].
Backfill: this event became public on Apr 7, 2025 and we added it on Nov 10, 2026. It is not a new event.
CISA Adds CrushFTP CrushFTP Vulnerability CVE-2025-31161 to Known Exploited Vulnerabilities Catalog
1 min read
- Disclosed
- Apr 7, 2025
- Published
- Nov 10, 2026
- Last updated
- Nov 8, 2026
- CVSS basis
- Our assessment
- 100%, higher than 100% of CVEs
- Exploitation and patch status
- ExploitedKEV
- Attack vector
- Vulnerability status
- Actor type
- Motivation
On this page
30-second summary
What happened
Who is affected
Industries mainly affected: Government, Cross-industry
What to do nowOur advice
CISA requires remediation in accordance with vendor mitigation instructions; see the original text in the body for specific requirements [2]
Timeline
Technical details
CISA KEV Listing Record
On 2025-04-07, CISA added CVE-2025-31161 to the catalog for CrushFTP CrushFTP [2].
Original Technical Description
CrushFTP contains an authentication bypass vulnerability in the HTTP authorization header that allows a remote unauthenticated attacker to authenticate to any known or guessable user account (e.g., crushadmin), potentially leading to a full compromise. [2]
Official Requirements
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. [2]
Individual Vulnerability Record
The U.S. National Vulnerability Database (NVD) provides an independent vulnerability record and description for CVE-2025-31161. [1]
References
Official / primary3
- [1]
“CrushFTP 10 before 10.8.4 and 11 before 11.3.1 allows authentication bypass and takeover of the crushadmin account (unless a DMZ proxy instance is used), as exploited in the wild in March and April 2025, aka "Unauthenticated HTTP(S) port access." A race condition exists in the AWS4-HMAC (compatible ”
- [2]
This site aggregates public information and is not security consulting advice. Test remediation steps before applying.