Private Field data leak

Exploitation

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

CVSS

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

EPSS

• CVE-2021-32624: 0.86% estimated exploitation activity in the next 30 days; percentile 58.69 (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.

This security advisory relates to a newly discovered capability in our query infrastructure to directly or indirectly expose the values of private fields, bypassing the configured access control. This is an access control related oracle attack in that the attack method guides an attacker during their attempt to reveal information they do not have access to. The complexity of completing the attack is limited by some length-dependent behaviors and the fidelity of the exposed information. Impact Under some circumstances, field values or field value meta data can be determined, despite the field or list having read access control configured. If you use private fields or lists, you may be impacted. Patches None, at this time Workarounds None, at this time References None For more information For the protection of the community and private deployments, we think that the best course of action will be to not disclose further details on any open GitHub issues related to this advisory until a…

Published by the source

27 May 2021, 18:39 UTC

Last modified by the source

8 Jul 2026, 06:27 UTC

Source last checked

26 Oct 2026, 12:20 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-27g8-r9vw-765x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-27g8-r9vw-765x

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

# Patch Next advisory brief: CVE-2021-32624

Advisory: Private Field data leak
IDs: CVE-2021-32624, GHSA-27g8-r9vw-765x
Record: https://patchnext.com/advisories/cve-2021-32624 (revision 2, source checked 26 Oct 2026, 12:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @keystonejs/keystone: affected <= 19.3.2

## Suggested inspection (read-only)
- `npm ls @keystonejs/keystone --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @keystonejs/keystone.
- 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://osv.dev/vulnerability/GHSA-27g8-r9vw-765x (OSV record GHSA-27g8-r9vw-765x lists affected ranges: npm @keystonejs/keystone >=0 <=19.3.2)
- Verified: https://github.com/advisories/GHSA-27g8-r9vw-765x (GitHub-reviewed advisory GHSA-27g8-r9vw-765x lists affected ranges: npm @keystonejs/keystone >=0 <=19.3.2)

Commands are suggestions: review each one before running it.