CVE-2025-57815: Fides has a Lack of Brute-Force Protections on Authentication Endpoints
Summary The Fides Admin UI login endpoint relies on a general IP-based rate limit for all API traffic and lacks specific anti-automation controls designed to protect against brute-force attacks. This could allow attackers to conduct credential testing attacks, such as credential stuffing or password spraying, which poses a risk to accounts with weak or previously compromised passwords.
Published Sep 8, 2025 · Updated Sep 13, 2025
Affected packages
ethyca-fides
- Ecosystem
- PyPI
- Affected
- < 2.69.1
- Fixed in
- 2.69.1
- Check
pip show ethyca-fides
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The Fides Admin UI login endpoint relies on a general IP-based rate limit for all API traffic and lacks specific anti-automation controls designed to protect against brute-force attacks. This could allow attackers to conduct credential testing attacks, such as credential stuffing or password spraying, which poses a risk to accounts with weak or previously compromised passwords.
Details
Fides uses a configurable, system-wide rate limit to control traffic from any single IP address. Because this single limit must be set high enough to accommodate endpoints that receive a large volume of legitimate traffic, it offers only weak protection for the login endpoint. The system is not equipped with more advanced protections tailored specifically for authentication
Impact
Although password complexity requirements and the global rate limit make a traditional brute-force attack against a single account difficult, the lack of authentication-specific protections exposes Fides to more targeted attacks. An attacker could use automated tools to test credentials obtained from data breaches or guess common passwords across multiple user accounts. If an attacker successfully compromises an account, they would gain full access to that user's privileges within the Fides Admin UI.
Patches
The vulnerability has been patched in Fides version 2.69.1. Users are advised to upgrade to this version or later to secure their systems against this threat.
Workarounds
For organizations with commercial Fides Enterprise licenses, configuring Single Sign-On (SSO) through an OIDC provider (like Azure, Google, or Okta) is an effective workaround. When OIDC SSO is enabled, username/password authentication can be disabled entirely, which eliminates this attack vector. This functionality is not available for Fides Open Source users.
Risk Level
This vulnerability has been assigned a severity of LOW.
This is fundamentally a security hardening issue. While the lack of authentication-specific rate limiting could enable credential stuffing attacks, several factors limit the risk: existing global rate limits provide baseline protection, password complexity requirements prevent trivial brute-force attacks, and successful exploitation requires attackers to already possess valid credentials from external breaches.
Credited to thabofletcher, daveqnet.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-44541
ethyca-fides has a DOM-based XSS vulnerability in fides.js via fides_description override
high7.0May 14, 2026CVE-2026-42303
Ethyca Fides has a Privacy Request Identity Verification Bypass Vulnerability via Duplicate Detection
medium6.1May 5, 2026CVE-2025-57766
Fides' Admin UI User Password Change Does Not Invalidate Current Session
low4.8Sep 8, 2025CVE-2025-57816
Fides Webserver API Rate Limiting Vulnerability in Proxied Environments
medium7.5Sep 8, 2025CVE-2025-57817
Fides Webserver API is Vulnerable to OAuth Client Privilege Escalation
high7.2Sep 8, 2025CVE-2024-52008
Password Policy Bypass Vulnerability in Fides Webserver User Accept Invite API
low5.7Nov 26, 2024
