NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2022-37315 — graphql

HIGHFix: graphql-go/graphql#642

CVE-2022-37315 is a high-severity (CVSS 7.5) CWE-674 vulnerability in github.com/graphql-go/graphql. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/graphql-go/graphql — see the affected versions and patch details below.

graphql-go has infinite recursion in the type definition parser

Also known asGHSA-h3qm-jrrf-cgj3GO-2022-0942
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.00%0.57%1.14%1.71%0.1%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/graphql-go/graphql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

graphql-go (aka GraphQL for Go) through 0.8.0 has infinite recursion in the type definition parser.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/graphql-go/graphqlall versions0.8.1go get github.com/graphql-go/graphql@v0.8.1

Affected Products

1 product · 1 configurations
Application
graphql-gographql-go_project
≤ 0.8.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/graphql-go/graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/graphql-go/graphql to 0.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37315 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

graphql-go (aka GraphQL for Go) through 0.8.0 has infinite recursion in the type definition parser.
O3 Security · Impact-Aware SCA

Is CVE-2022-37315 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2022-37315: graphql — Fixed in 0.8.1