Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2025-8696

DoS attack against the Stork UI from an unauthenticated user

High7.5EPSS 0.46%
Published
Updated
Reserved
Assigned by
isc

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.

Scores

CVSS scores of CVE-2025-8696, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Deferred3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.46% · top 60% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Weakness

Affected products

  • ISC · Stork

    • affected 1.0.0 – ≤ 2.3.0

What to do

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.

Exploitation: This flaw was discovered in internal testing. We are not aware of any active exploits.

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-8696 badge
[![CVE-2025-8696](https://trackcve.app/badge/CVE-2025-8696.svg)](https://trackcve.app/cve/CVE-2025-8696)

Record last updated .