Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

vercel

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 5.5npmAmendedPublished

    Vercel: Non-interactive mode includes CLI arguments in suggested command output

    CVE-2026-44479 · GHSA-pgf8-2hgj-grqg

    Affected
    • npm vercel >= 50.16.0, <= 52.0.0
    Fixed in
    52.0.1· Vendor fix available
    Issue
    When the Vercel CLI runs in non-interactive mode (--non-interactive or auto-detected AI agent), commands that cannot complete autonomously emit JSON payloads with suggested follow-up commands. If the user authenticated via --token or -t on the command line, the token value is included verbatim in those suggestions. Conditions All three must be true for the token to appear in output: 1. Token passed as a CLI argument (--token / -t). The VERCELTOKEN environment variable is not affected. 2. Non-interactive mode is active (explicit flag or AI agent auto-detection). 3. The command cannot complete on its own (e.g. missing --yes, ambiguous scope, API errors). Successful commands produce no suggestion output. Impact The plaintext token may be captured in CI/CD logs, agent transcripts, or other automation output. Remediation - Upgrade to the patched version. - If developers have previously used --token with --non-interactive in their applications, review logs for exposed tokens and…

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