CVE-2025-8696: DoS attack against the Stork UI from an unauthenticated user
If an unauthenticated user sends a large amount of data to the Stork UI, it may cause memory and disk use problems for the system running the Stork server. This issue affects Stork versions 1.0.0 through 2.3.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Storkto a version that resolves this vulnerability.Fixed in 2.2.1 - Upgrade
Upgrade
Storkto a version that resolves this vulnerability.Fixed in 2.3.1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-8696?
CVE-2025-8696 is classified as a moderate severity vulnerability due to its potential impact on system resources.
How do I fix CVE-2025-8696?
To mitigate CVE-2025-8696, update Stork to version 2.3.1 or later, which addresses the issue.
Who is affected by CVE-2025-8696?
CVE-2025-8696 affects users running Stork versions 1.0.0 through 2.3.0.
What are the potential consequences of CVE-2025-8696?
The potential consequences of CVE-2025-8696 include significant memory and disk usage problems for the Stork server.
Can CVE-2025-8696 be exploited remotely?
Yes, CVE-2025-8696 can be exploited by an unauthenticated user sending a large amount of data to the Stork UI.