CVE-2026-82291

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. the CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, ghsa
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.1
EG Score
8.1(high)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (5)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

HeyForm Reflects Any Origin in CORS Responses While Allowing Credentials | Advisories | VulnCheck

https://www.vulncheck.com/advisories/heyform-reflects-any-origin-in-cors-responses-while-allowing-credentials
generic

GitHub - heyform/heyform: Open-Source Form Builder · GitHub

https://github.com/heyform/heyform
github_commit Patch Available

commit bf9d738ca70a (heyform/heyform)

Patch available: heyform/heyform v3.0.0-rc.8 (contains commit bf9d738ca70a)

https://github.com/heyform/heyform/commit/bf9d738ca70ae5641c0c7372982b00365c5144d4
generic

heyform/packages/server/src/main.ts at v3.0.0-rc.7 · heyform/heyform · GitHub

https://github.com/heyform/heyform/blob/v3.0.0-rc.7/packages/server/src/main.ts
github Patch Available🟡 PoC Available

Unauthenticated Cross-Origin Data Theft via CORS Wildcard Reflection with Credentials · Advisory · heyform/heyform · GitHub

https://github.com/heyform/heyform/security/advisories/GHSA-fg7j-rmgr-rc9g

Vendor Advisories for CVE-2026-82291(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:23 UTCGHSA enrichment
  3. 2026-08-29 11:58 UTCEG score recompute
  4. 2026-08-29 11:58 UTCGHSA enrichment
  5. 2026-08-29 07:52 UTCEG score recompute
  6. 2026-08-29 07:51 UTCGHSA enrichment
  7. 2026-08-28 20:25 UTCEG score recompute
  8. 2026-08-28 19:39 UTCEG score recompute
  9. 2026-08-28 19:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82291?
CVE-2026-82291 is a high vulnerability published on August 28, 2026. 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,…
When was CVE-2026-82291 disclosed?
CVE-2026-82291 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82291 actively exploited?
CVE-2026-82291 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.9% of all scored CVEs.
What is the CVSS score of CVE-2026-82291?
CVE-2026-82291 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-82291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82291, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82291

Explore →

Is Your Infrastructure Affected by CVE-2026-82291?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs