First published: Mon Apr 28 2025(Updated: )
### Impact n8n workflows can store and serve binary files, which are accessible to authenticated users. However, there was no restriction on the MIME type of uploaded files, and the MIME type could be controlled via a GET parameter. This allowed the server to respond with any MIME type, potentially enabling malicious content to be interpreted and executed by the browser. An authenticated attacker with member-level permissions could exploit this by uploading a crafted HTML file containing malicious JavaScript. When another user visits the binary data endpoint with the MIME type set to text/html, the script executes in the context of the user’s session. This script could, for example, send a request to change the user’s email address in their account settings, effectively enabling account takeover. ### Patches - [n8n@1.90.0](https://github.com/n8n-io/n8n/releases/tag/n8n%401.90.0) ### Credit We would like to thank @Mahmoud0x00 for reporting this issue.
Affected Software | Affected Version | How to fix |
---|---|---|
npm/n8n | <1.90.0 | 1.90.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of GHSA-c8hm-hr8h-5xjw is classified as a high risk due to unrestricted MIME types which can lead to potential security vulnerabilities.
To fix GHSA-c8hm-hr8h-5xjw, upgrade n8n to version 1.90.0 or later where the issue has been resolved.
GHSA-c8hm-hr8h-5xjw affects users of n8n versions prior to 1.90.0 that allow unrestricted MIME type uploads.
The impact of GHSA-c8hm-hr8h-5xjw includes the possibility of serving malicious files due to unrestricted MIME type handling.
GHSA-c8hm-hr8h-5xjw occurs when n8n workflows do not validate MIME types for uploaded binary files, allowing user-controlled MIME type parameters.