Skip to content

← Public intelligence

npm package

estree-util-value-to-estree

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

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

  1. Medium, CVSS 6.9npmAmendedPublished

    estree-util-value-to-estree allows prototype pollution in generated ESTree

    CVE-2025-32014 · GHSA-f7f6-9jq7-3rqj

    Affected
    • npm estree-util-value-to-estree < 3.3.3
    Fixed in
    3.3.3· Vendor fix available
    Issue
    Impact When generating an ESTree from a value with a property named proto, valueToEstree would generate an object that specifies a prototype instead. Example: Output: Patches This was fixed in version 3.3.3. Workarounds If you control the input, don’t specify a property named proto. If you don’t control the output, strip any properties named proto before passing it to valueToEstree.

    Recommended action: Upgrade to 3.3.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 →