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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-08-28).

Weakness: Permissive Cross-domain Security Policy with Untrusted Domains

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 2 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 5 references on Exploit Observer

Live scores

EPSS
0.006
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei

Who is affected

ProductAffectedNot affected
heyformbefore 3.0.0-rc.8Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 3.0.0-rc.8.

Vendor guidance:

How to detect it

Nuclei template (active check)

HeyForm - CORS Misconfiguration

HeyForm before 3.0.0-rc.8 configures its NestJS server with app.enableCors({ origin: true, credentials: true }), which reflects the request Origin header in the Access-Control-Allow-Origin response while also sending Access-Control-Allow-Credentials: true. A malicious page visited by a logged-in user can issue credentialed cross-origin GraphQL requests to read workspaces, projects, forms, submissions and respondent data or modify account settings.

Name and description quoted from the template, written by VEDAS.

The template sends 2 requests (GET /, OPTIONS /graphql); it decides using dsl matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-82291.yaml
Show the template (60 lines)
yaml
id: CVE-2026-82291

info:
  name: "HeyForm - CORS Misconfiguration"
  author: vedas-arpsyndicate
  severity: high
  description: |
    HeyForm before 3.0.0-rc.8 configures its NestJS server with
    app.enableCors({ origin: true, credentials: true }), which reflects the request Origin header in the
    Access-Control-Allow-Origin response while also sending Access-Control-Allow-Credentials: true. A malicious
    page visited by a logged-in user can issue credentialed cross-origin GraphQL requests to read workspaces,
    projects, forms, submissions and respondent data or modify account settings.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-82291&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=heyform&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
    cvss-score: 8.1
    cve-id: CVE-2026-82291
    cwe-id: CWE-942
  metadata:
    verified: false
  tags: cve,cve2026,heyform,cors,misconfig
flow: http(1) && http(2)

http:
  - raw:
      - |
        GET / HTTP/1.1
        Host: {{Hostname}}

    redirects: true
    max-redirects: 3

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(tolower(body), "heyform")'
        condition: and
        internal: true

  - raw:
      - |
        OPTIONS /graphql HTTP/1.1
        Host: {{Hostname}}
        Origin: {{cors_origin}}
        Access-Control-Request-Method: POST
        Access-Control-Request-Headers: authorization,content-type

    payloads:
      cors_origin:
        - "https://{{tolower(rand_base(5))}}.example.com"

    matchers:
      - type: dsl
        dsl:
          - 'contains(tolower(header), "access-control-allow-origin: {{cors_origin}}")'
          - 'contains(tolower(header), "access-control-allow-credentials: true")'
        condition: and

CVE-2026-82291.yaml on GitHub

References

Vendor advisories and patches

Technical analysis and advisories

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners