Unauthenticated process crash via oversized UI input
Published Sep 10, 2025 · Updated Nov 4, 2025
Resource exhaustion in Internet Systems Consortium Stork 1.0.0 through 2.3.0 allows remote attackers to crash processes via large UI input. The UI request path accepts unauthenticated oversized input and allocates memory for it; repeated smaller inputs also consume log storage, although ISC has not disclosed the exact endpoint or handler. No account is required, and successful exploitation can terminate stork-server or other processes or fill available log storage.
Summary
What happened
Resource exhaustion in Internet Systems Consortium Stork 1.0.0 through 2.3.0 allows remote attackers to crash processes via large UI input. The UI request path accepts unauthenticated oversized input and allocates memory for it; repeated smaller inputs also consume log storage, although ISC has not disclosed the exact endpoint or handler. No account is required, and successful exploitation can terminate stork-server or other processes or fill available log storage.
The record
- CVE
- CVE-2025-8696
- Published
- Sep 10, 2025
- Updated
- Nov 4, 2025
- Vendor
- Internet Systems Consortium
- Product
- Stork
- Classifications
- CWE-779, CWE-789, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=1.0.0 <=2.3.0
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