Rate-limit bypass via edge-node rotation
Published Jul 25, 2025 · Updated Jul 25, 2025
Rate-limit bypass in Akamai Rate Control alpha before 2025 allows remote attackers to exceed configured request thresholds. Rate Control stores threshold state separately at each edge node instead of aggregating it globally, so rotating requests among Akamai edge servers resets the effective accounting boundary. No authentication or user interaction is required; exploitation depends on reaching multiple edge nodes and can degrade the protected origin's availability with excess traffic.
Summary
What happened
Rate-limit bypass in Akamai Rate Control alpha before 2025 allows remote attackers to exceed configured request thresholds. Rate Control stores threshold state separately at each edge node instead of aggregating it globally, so rotating requests among Akamai edge servers resets the effective accounting boundary. No authentication or user interaction is required; exploitation depends on reaching multiple edge nodes and can degrade the protected origin's availability with excess traffic.
The record
- CVE
- CVE-2025-54568
- Published
- Jul 25, 2025
- Updated
- Jul 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-684, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2025CVE publishedPublication date reported by the CVE source.
- Jul 25, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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