DoS attack against the Stork UI from an unauthenticated user

published 2025-09-10 13 mo ago modified 2026-09-26 44 d ago also EUVD-2025-27598

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

isc stork 2.2.1, 2.3.1

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 13 mo ago (2025-09-11)

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

ISC Stork

Classification

Weakness

CWE-789 Memory Allocation with Excessive Size Value
CWE-779 Logging of Excessive Data

References

kb.isc.org /docs/cve-2025-8696
vendor-advisory
openwall.com /lists/oss-security/2025/09/10/5

Sources

CVE List CVE-2025-8696
NVD CVE-2025-8696

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary