Skip to content

← Public intelligence

npm package

ajv

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.5npmAmendedPublished

    ajv has ReDoS when using $data option

    CVE-2025-69873 · GHSA-2g4f-4pwh-qvx6

    Affected
    • npm ajv >= 7.0.0-alpha.0, < 8.18.0; < 6.14.0
    Fixed in
    6.14.08.18.0· Vendor fix available
    Issue
    ajv (Another JSON Schema Validator) through version 8.17.1 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is enabled. The pattern keyword accepts runtime data via JSON Pointer syntax ($data reference), which is passed directly to the JavaScript RegExp() constructor without validation. An attacker can inject a malicious regex pattern (e.g., \"^(a|a)$\") combined with crafted input to cause catastrophic backtracking. A 31-character payload causes approximately 44 seconds of CPU blocking, with each additional character doubling execution time. This enables complete denial of service with a single HTTP request against any API using ajv with $data: true for dynamic schema validation.

    Recommended action: Upgrade to 8.18.0 or 6.14.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 5.6npmAmendedPublished

    Prototype Pollution in Ajv

    CVE-2020-15366 · GHSA-v88g-cgmw-v5xw

    Affected
    • npm ajv < 6.12.3
    Fixed in
    6.12.3· Vendor fix available
    Issue
    An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)

    Recommended action: Upgrade to 6.12.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →