# CVE-2026-82291: HeyForm Reflects Any Origin in CORS Responses While Allowing Credentials

> HeyForm reflects any Origin in CORS responses with credentials, allowing attackers to execute authenticated GraphQL queries to read or modify user data.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-69g7-vm8m-997r, GHSA-fg7j-rmgr-rc9g

## What is CVE-2026-82291?

CVE-2026-82291 is a high-severity vulnerability in heyform, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

## Which versions are affected by CVE-2026-82291?


## How do I fix CVE-2026-82291?

No fix has been published for CVE-2026-82291 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82291 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82291 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82291 and fix it if it is affected.

What it is: CVE-2026-82291 is a high-severity vulnerability in heyform, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82291 exists.

Affected product: heyform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82291/ (Markdown: https://insights.sbomify.com/CVE-2026-82291/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82291
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82291
- OSV: https://osv.dev/vulnerability/CVE-2026-82291

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82291/
Summaries are generated and may contain mistakes; the official description above is the record.