CVE-2025-24033: @fastify/multipart vulnerable to unlimited consumption of resources

Published Jan 23, 2025
·
Updated

@fastify/multipart is a Fastify plugin for parsing the multipart content-type. Prior to versions 8.3.1 and 9.0.3, the saveRequestFiles function does not delete the uploaded temporary files when user cancels the request. The issue is fixed in versions 8.3.1 and 9.0.3. As a workaround, do not use saveRequestFiles.

Other sources

Impact

The saveRequestFiles function does not delete the uploaded temporary files when user cancels the request.

Patches

Fixed in version 8.3.1 and 9.0.3

Workarounds

Do not use saveRequestFiles.

References

This was identified in https://github.com/fastify/fastify-multipart/issues/546 and fixed in https://github.com/fastify/fastify-multipart/pull/567.

GitHub

Affected Software

3 affected componentsFixes available
npm/@fastify/multipart>=9.0.0<9.0.3
9.0.3
npm/@fastify/multipart<=8.3.0
8.3.1
fastify multipart<8.3.1, <9.0.3

Event History

Jan 23, 2025
CVE Published
via MITRE·05:40 PM
Data Sourced
via MITRE·05:40 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:02 PM
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-24033?

CVE-2025-24033 is classified as a moderate severity vulnerability due to the potential for data leakage from unremoved temporary files.

2

How do I fix CVE-2025-24033?

To fix CVE-2025-24033, you should upgrade the @fastify/multipart package to version 9.0.3 or 8.3.1.

3

What problem does CVE-2025-24033 cause?

CVE-2025-24033 occurs because the saveRequestFiles function does not delete uploaded temporary files when a user cancels a request.

4

Which versions of @fastify/multipart are affected by CVE-2025-24033?

Versions of @fastify/multipart prior to 8.3.1 and 9.0.3 are affected by CVE-2025-24033.

5

Is there a workaround for CVE-2025-24033?

While the ideal solution is to upgrade, implementing manual cleanup of temporary files can serve as a workaround for CVE-2025-24033.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203