CVE-2026-82291Public exploitNetwork attack vectorHinoki check available

Cross-origin data theft via credentialed origin reflection

Published Aug 28, 2026 · Updated Aug 29, 2026

Improper CORS policy in HeyForm before 3.0.0-rc.8 allows remote attackers to read or modify authenticated GraphQL data. The server's enableCors call in packages/server/src/main.ts sets origin to true and credentials to true, echoing every request Origin while permitting browsers to expose credentialed responses. Exploitation requires a logged-in user to visit an attacker-controlled page; the page can then read workspace and respondent data or issue account and content mutations with the user's cookies.

CVSS severity8.1
High
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper CORS policy in HeyForm before 3.0.0-rc.8 allows remote attackers to read or modify authenticated GraphQL data. The server's enableCors call in packages/server/src/main.ts sets origin to true and credentials to true, echoing every request Origin while permitting browsers to expose credentialed responses. Exploitation requires a logged-in user to visit an attacker-controlled page; the page can then read workspace and respondent data or issue account and content mutations with the user's cookies.

The record

CVE
CVE-2026-82291
Published
Aug 28, 2026
Updated
Aug 29, 2026
Vendor
HeyForm
Product
HeyForm
Classifications
CWE-942, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 29, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <3.0.0-rc.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

HeyForm · HeyFormversion=0 <3.0.0-rc.8

Published CVSS scores

9.3HeyForm GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
8.1VulnCheck CNACVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-942Permissive Cross-domain Security Policy with Untrusted Domains
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo