Denial of Service in graphql-go

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2022-21708: 1.24% estimated exploitation activity in the next 30 days; percentile 69.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This is a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using graphql.MaxDepth option in your schema (which is highly recommended in most cases). Patches The issue has been patched in version v1.3.0. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic. Workarounds The best workaround is to patch to a version greater than or equal to v1.3.0. Otherwise, the only workaround in versions prior to v1.3.0 is to disable the graphql.MaxDepth option from your schema.…

Published by the source

27 Jan 2022, 15:28 UTC

Last modified by the source

9 Feb 2023, 20:06 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mh3m-8c74-74xh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-21708

Advisory: Denial of Service in graphql-go
IDs: CVE-2022-21708, GHSA-mh3m-8c74-74xh
Record: https://patchnext.com/advisories/cve-2022-21708 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/graph-gophers/graphql-go 1.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/graph-gophers/graphql-go: affected < 1.3.0; fixed in 1.3.0

## Suggested inspection (read-only)
- Go github.com/graph-gophers/graphql-go: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/graph-gophers/graphql-go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mh3m-8c74-74xh (GitHub-reviewed advisory GHSA-mh3m-8c74-74xh lists affected ranges: Go github.com/graph-gophers/graphql-go >=0 <1.3.0)

Commands are suggestions: review each one before running it.