Homepage

@keystone-6/core@0.0.0-rc-20250625234121

  • latest version

    8.0.4

  • first published

    4 years ago

  • latest version published

    5 days ago

  • View core package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @keystone-6/core package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Allocation of Resources Without Limits or Throttling

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the GraphQL API Endpoint that lacks depth limiting and complexity analysis for SQL queries. An attacker can cause excessive resource consumption by sending specially crafted requests (such as deeply-nested circular relationship query) to the affected endpoint.

    How to fix Allocation of Resources Without Limits or Throttling?

    There is no fixed version for @keystone-6/core.

    *
    • L
    Information Exposure

    Affected versions of this package are vulnerable to Information Exposure when applying isFilterable to sensitive data. By adding malicious uniqueness filters to the where clause of an update or delete operation, a user can infer the presence of specific values in records the user does not have permission to read.

    Notes:

    1. This vulnerability has no impact on fields to which isFilterable: false or defaultIsFilterable: false are applied

    2. This is caused by an incomplete fix for CVE-2025-46720

    How to fix Information Exposure?

    Upgrade @keystone-6/core to version 6.5.2 or higher.

    <6.5.2
    • L
    Information Exposure

    Affected versions of this package are vulnerable to Information Exposure when applying isFilterable to sensitive data. By adding malicious uniqueness filters to the where clause of an update or delete operation, a user can infer the presence of specific values in records the user does not have permission to read.

    Note: This vulnerability has no impact on fields to which isFilterable: false or defaultIsFilterable: false are applied.

    How to fix Information Exposure?

    Upgrade @keystone-6/core to version 6.5.0 or higher.

    <6.5.0
    • L
    Improper Access Control

    Affected versions of this package are vulnerable to Improper Access Control when ui.isAccessAllowed is set as undefined, the adminMeta GraphQL query is publicly accessible (no session required). This is different from the behavior of the default AdminUI middleware, which by default will only be publicly accessible (no session required) if a session strategy is not defined.

    How to fix Improper Access Control?

    Upgrade @keystone-6/core to version 5.5.1 or higher.

    <5.5.1
    Go back to all versions of this package