GHSA-CQMQ-8755-7XVH

Vulnerability from github – Published: 2026-08-21 20:55 – Updated: 2026-08-21 20:55
VLAI
Summary
Keystone vulnerable to `graphql.maxTake` bypass with negative `take`
Details

Summary

The value of graphql.maxTake can be bypassed by providing a negative input. This can be used to exceed the developer's intended graphql.maxTake value, allowing queries to return results in excess of the graphql.maxTake value set.

Impact

This affects any project relying on graphql.maxTake to bound the number of items returned per query.

Patches

This issue has been patched in @keystone-6/core version 6.5.3.

If you cannot patch, you can workaround this by restricting take input values in your GraphQL queries to the bounded value, or by blocking negative values.

Credit

This issue was found by Haxset's Security Scanner and validated by their team.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 6.5.2"
      },
      "package": {
        "ecosystem": "npm",
        "name": "@keystone-6/core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.5.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-63421"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20",
      "CWE-480"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-21T20:55:11Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "# Summary\nThe value of `graphql.maxTake` can be bypassed by providing a negative input.\nThis can be used to exceed the developer\u0027s intended `graphql.maxTake` value, allowing queries to return results in excess of the `graphql.maxTake` value set.\n\n# Impact\nThis affects any project relying on `graphql.maxTake` to bound the number of items returned per query.\n\n# Patches\nThis issue has been patched in `@keystone-6/core` version `6.5.3`.\n\nIf you cannot patch, you can workaround this by restricting `take` input values in your GraphQL queries to the bounded value, or by blocking negative values.\n\n# Credit\nThis issue was found by [Haxset\u0027s](https://haxset.com) Security Scanner and validated by their team.",
  "id": "GHSA-cqmq-8755-7xvh",
  "modified": "2026-08-21T20:55:11Z",
  "published": "2026-08-21T20:55:11Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/keystonejs/keystone/security/advisories/GHSA-cqmq-8755-7xvh"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keystonejs/keystone/pull/9859"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keystonejs/keystone/commit/9fb88b246950ce4de754a43fe6416f20403577b1"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/keystonejs/keystone"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keystonejs/keystone/releases/tag/@keystone-6/core@6.5.3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Keystone vulnerable to `graphql.maxTake` bypass with negative `take`"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.