github.com/graphql-go/graphql (GraphQL for Go) through 0.8.1 does not validate that a scalar variable value matches its declared type. The built-in coerceString and coerceBool functions (scalars.go) accept input whose type does not match the declared String, ID, or Boolean scalar instead of raising the request error that the GraphQL specification mandates. In some cases (but not any typical case of JSON sent to a website), a deeply nested value leads to an unrecoverable "fatal error: stack overflow" condition.
CVE-2026-80051
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(low)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity59% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026oss-security - graphql-go/graphql <= 0.8.1: improper scalar input-type validation -> type confusion and unrecoverable stack-overflow DoS
https://www.openwall.com/lists/oss-security/2026/08/25/2graphql/scalars.go at v0.8.1 · graphql-go/graphql · GitHub
https://github.com/graphql-go/graphql/blob/v0.8.1/scalars.go#L307-L315Vendor Advisories for CVE-2026-80051(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 7× in last 7d / 7× 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.
- 2026-08-25 20:23 UTCEG score recompute
- 2026-08-25 20:23 UTCGHSA enrichment
- 2026-08-25 19:36 UTCEG score recompute
- 2026-08-25 19:36 UTCGHSA enrichment
- 2026-08-25 18:26 UTCEG score recompute
- 2026-08-25 18:05 UTCEG score recompute
- 2026-08-25 18:04 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-80051?
When was CVE-2026-80051 disclosed?
What is the CVSS score of CVE-2026-80051?
How do I remediate CVE-2026-80051?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-80051
Is Your Infrastructure Affected by CVE-2026-80051?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.