CVE-2026-82291
HeyForm before 3.0.0-rc.8 reflects the request Origin header in CORS responses while allowing credentials, enabling cross-origin requests with authentication.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.30%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
HeyForm before 3.0.0-rc.8 reflects the request Origin header in CORS responses while allowing credentials, enabling cross-origin requests with authentication. Attackers can execute authenticated GraphQL queries from malicious pages visited by logged-in users to access workspaces, projects, forms, submissions, and respondent data, or modify account settings.
- CVSS 3.1
- 8.1 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
- EPSS
- 0.30% probability · 23th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-942
- Source
- disclosure@vulncheck.com
References
- https://github.com/heyform/heyform
- https://github.com/heyform/heyform/blob/v3.0.0-rc.7/packages/server/src/main.ts
- https://github.com/heyform/heyform/commit/bf9d738ca70ae5641c0c7372982b00365c5144d4
- https://github.com/heyform/heyform/security/advisories/GHSA-fg7j-rmgr-rc9g
- https://www.vulncheck.com/advisories/heyform-reflects-any-origin-in-cors-responses-while-allowing-credentials
- https://github.com/heyform/heyform/security/advisories/GHSA-fg7j-rmgr-rc9g
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.