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.
Fixes

Solution

Upgrade to the patched release most closely related to your current version of Stork: 2.2.1 or 2.3.1.


Workaround

Placing the Stork server behind a firewall or proxy that only allows access from trusted clients, and/or enforces input size limits, is an effective workaround.

References
History

Wed, 10 Sep 2025 18:15:00 +0000

Type Values Removed Values Added
Description 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.
Title DoS attack against the Stork UI from an unauthenticated user
Weaknesses CWE-779
CWE-789
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: isc

Published:

Updated: 2025-09-10T17:59:52.878Z

Reserved: 2025-08-07T09:49:55.542Z

Link: CVE-2025-8696

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2025-09-10T18:15:34.817

Modified: 2025-09-10T18:15:34.817

Link: CVE-2025-8696

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.