CVE-2026-82291
Reflected Origin CORS + credentials in HeyForm enables authenticated cross-origin GraphQL access.
Is CVE-2026-82291 being exploited?
Not confirmed. CVE-2026-82291 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-82291?
CVE-2026-82291 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82291?
Yes. A fix has been recorded for CVE-2026-82291. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82291 affect?
CVE-2026-82291 affects HeyForm < 3.0.0-rc.8, heyform/server package (GitHub). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82291?
Upgrade HeyForm to v3.0.0-rc.8+; restrict CORS origins and rotate exposed credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can perform authenticated cross-origin GraphQL requests to read/exfiltrate workspaces, projects, forms, submissions, respondent data, and change account settings.
Immediate action required
- affected< 3.0.0-rc.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.