Quick answers
- Is CVE-2026-45797 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45797 being exploited in the wild.
- How severe is CVE-2026-45797?
- Informational severity, with a CVSS score of 6.4, published 20 July 2026.
- Which products and versions are affected?
- HeyForm < 3.0.0-rc.7.
- Is there a fix for CVE-2026-45797?
- A patch was published on 2026-07-20: Fix confirmed in version 3.0.0-rc.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45797 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45797?
- Check whether you run HeyForm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
HeyForm prior to version 3.0.0-rc.7 contains a stored cross-site scripting (XSS) vulnerability due to unrestricted file uploads. The `/api/upload` endpoint lacks an `@Auth()` decorator, allowing unauthenticated users to upload SVG files. Because the application's Express `serve-static` middleware serves these files with the `image/svg+xml` MIME type, any embedded JavaScript within the SVG is executed in the context of the victim's browser session when the file is accessed. This allows attackers to perform actions on behalf of users, such as stealing session cookies or executing GraphQL mutations. The issue is fixed in version 3.0.0-rc.7 by blocking SVG uploads and hardening the static file serving configuration.
Affected products
- HeyForm HeyForm < 3.0.0-rc.7
Timeline
- 2026-05-14: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: CVE published to NVD
- 2026-07-20: patched: Fix confirmed in version 3.0.0-rc.7