Service interruption via misattributed in-memory rate limits
Published Sep 8, 2025 · Updated Sep 9, 2025
Improper rate limiting in Fides before 2.69.1 allows remote attackers to interrupt API service through unauthenticated requests. The Webserver API keys request counters to directly connected proxy addresses and keeps those counters in each process instead of a shared store. Exploitation requires a proxied deployment that relies on the built-in limiter; attackers can exhaust resources or force legitimate clients to receive HTTP 429 responses.
Summary
What happened
Improper rate limiting in Fides before 2.69.1 allows remote attackers to interrupt API service through unauthenticated requests. The Webserver API keys request counters to directly connected proxy addresses and keeps those counters in each process instead of a shared store. Exploitation requires a proxied deployment that relies on the built-in limiter; attackers can exhaust resources or force legitimate clients to receive HTTP 429 responses.
The record
- CVE
- CVE-2025-57816
- Published
- Sep 8, 2025
- Updated
- Sep 9, 2025
- Vendor
- Ethyca
- Product
- Fides
- Classifications
- CWE-799, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2025CVE publishedPublication date reported by the CVE source.
- Sep 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.69.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo