Unauthenticated service interruption via unbounded JavaScript evaluation
Published Aug 21, 2025 · Updated Aug 21, 2025
Uncontrolled resource consumption in pyLoad before 0.5.0b3.dev92 allows remote attackers to interrupt the web UI through a crafted request. The /flash/addcrypted2 handler passes the unvalidated jk form value into eval_js, allowing supplied JavaScript to execute an arbitrarily long loop. The endpoint requires no authentication but applies a local-origin check; successful requests saturate server CPU and leave the web UI unresponsive.
Summary
What happened
Uncontrolled resource consumption in pyLoad before 0.5.0b3.dev92 allows remote attackers to interrupt the web UI through a crafted request. The /flash/addcrypted2 handler passes the unvalidated jk form value into eval_js, allowing supplied JavaScript to execute an arbitrarily long loop. The endpoint requires no authentication but applies a local-origin check; successful requests saturate server CPU and leave the web UI unresponsive.
The record
- CVE
- CVE-2025-57751
- Published
- Aug 21, 2025
- Updated
- Aug 21, 2025
- Vendor
- pyLoad
- Product
- pyLoad
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2025CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=< 0.5.0b3.dev92
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.
Public exploit references
- GHSA curl CPU-exhaustion proof of conceptproof of concept · demonstrated
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