@keystone-6/core's bundled cuid package known to be insecure

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The cuid package used by @keystone-6/ and upstream dependencies is deprecated and marked as insecure by the author. As reported by the author Cuid and other k-sortable and non-cryptographic ids (Ulid, ObjectId, KSUID, all UUIDs) are all insecure. Use @paralleldrive/cuid2 instead. What are doing about this? - We are waiting on Prisma to add support for cuid2 - Alternatively, we might default to a random string ourselves What can I do about this? We have added a work-around for users who want to provide custom identifiers in https://github.com/keystonejs/keystone/pull/8645 What if I need a cuid? The features marked as a security vulnerability by @paralleldrive are sometimes actually needed (as written in the README of cuid) - the problem is the inherent risks that features like this can have. You might actually want the features of a monotonically increasing (auto-increment, k-sortable), and timestamp-based id as part of your application, and keystone should support that - but…

Published by the source

12 Jun 2023, 18:37 UTC

Last modified by the source

23 Jun 2023, 13:56 UTC

Source last checked

26 Oct 2026, 12:22 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5fp6-4xw3-xqq3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5fp6-4xw3-xqq3

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

# Patch Next advisory brief: GHSA-5fp6-4xw3-xqq3

Advisory: @keystone-6/core's bundled cuid package known to be insecure
IDs: GHSA-5fp6-4xw3-xqq3
Record: https://patchnext.com/advisories/ghsa-5fp6-4xw3-xqq3 (revision 2, source checked 26 Oct 2026, 12:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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 @keystone-6/core: affected <= 5.3.1

## Suggested inspection (read-only)
- `npm ls @keystone-6/core --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 @keystone-6/core.
- 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-5fp6-4xw3-xqq3 (OSV record GHSA-5fp6-4xw3-xqq3 lists affected ranges: npm @keystone-6/core >=0 <=5.3.1)
- Verified: https://github.com/advisories/GHSA-5fp6-4xw3-xqq3 (GitHub-reviewed advisory GHSA-5fp6-4xw3-xqq3 lists affected ranges: npm @keystone-6/core >=0 <=5.3.1)

Commands are suggestions: review each one before running it.