Skip to main content
CVE-2025-8696VulnerabilityPublished Updated

If an unauthenticated user sends a large amount of data to the Stork UI, it may cause memory and disk use problems for

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-8696· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 4 Nov 2026, 17:57 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (isc)CVSS 3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

AI-suggested

Until a fix is available, consider implementing network-level rate limiting or filtering to restrict large or abnormal data submissions to the Stork UI. Monitor system resource usage to detect potential exploitation attempts.

Description

CVE-2025-8696 is a vulnerability in Stork UI versions 1.0.0 through 2.3.0 where an unauthenticated user can send a large amount of data to the interface, potentially causing excessive memory and disk usage on the system hosting the Stork server. This can lead to denial of service conditions due to resource exhaustion.

References

Community reviews

Loading reviews…