Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

lightning-flow-scanner

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. High, CVSS 8.4npmAmendedPublished

    Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of new Function() in APIVersion Rule

    CVE-2025-67750 · GHSA-55jh-84jv-8mx8

    Affected
    • npm lightning-flow-scanner < 6.10.6
    Fixed in
    6.10.6· Vendor fix available
    Issue
    Impact The APIVersion rule uses new Function() to evaluate expression strings. A malicious crafted flow metadata file can cause arbitrary JavaScript execution during scanning. An attacker could execute arbitrary JavaScript during a scan by supplying a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments. Patches The patch removes all uses of new Function() and replaces them with a safer parser. It now validates operators (, =, <, <=, ==) and performs numeric comparisons without evaluating untrusted JavaScript. version: core-v6.10.6, version vsx:: v2.4.4 version app:: v3.1.0 Work around

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