@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 3.0.0 through 10.1.3, temporary files written by the saveRequestFiles helper are removed only by a response hook that runs when the response finishes or errors. When a client completes an upload and then disconnects before the handler writes the reply, for example while the handler scans, hashes or forwards the file, the response only emits a close event, the cleanup hook never runs, and the saved files are left on disk. An unauthenticated client can repeat this cheaply to exhaust disk space and deny service to applications that save uploaded files to disk. The issue is fixed in @fastify/multipart 10.1.4, and users should upgrade to 10.1.4 or later. As a workaround, avoid saving request files for untrusted clients, or clean the saved files from a close handler on the raw response so removal also happens when the client disconnects.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
The @fastify/multipart plugin versions 3.0.0 through 10.1.3 contain a resource management flaw where temporary files uploaded by clients are not properly cleaned up when the client disconnects before the handler completes processing. The vulnerability stems from cleanup logic that depends on a response finish/error hook—a hook that never executes if the client closes the connection while the handler is still scanning, hashing, or forwarding the file. This leaves orphaned temporary files on disk indefinitely, leading to disk space exhaustion and potential denial of service. Any application using the vulnerable versions of @fastify/multipart for file uploads is at risk, particularly those handling high volumes of uploads or processing large files.
While this CVE does not map directly to MITRE ATT&CK techniques, Casky's security practitioners would detect the underlying attack patterns through resource exhaustion and unclean shutdown indicators. Extended reasoning across Casky's 754 mapped skills would surface defensive gaps around T1499 (Endpoint Denial of Service) and T1070 (Indicator Removal), helping teams identify monitoring blind spots for orphaned file accumulation, abnormal disk usage patterns, and incomplete cleanup cycles. Practitioners using Casky would see findings highlighting the need for explicit file lifecycle management, timeout enforcement on upload handlers, and monitoring for stale temporary directories—shifting detection from post-exploitation cleanup failures to proactive handler design reviews.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-110710. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation