CVE-2026-44479

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 VERCEL_TOKEN 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.

The plaintext token may be captured in CI/CD logs, agent transcripts, or other automation output.

CVE-2026-44479 has a CVSS score of 5.5 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (52.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

• Upgrade to the patched version.
• If developers have previously used --token with --non-interactive in their applications, review logs for exposed tokens and rotate them.
• Prefer VERCEL_TOKEN environment variable for authentication.

1. What is CVE-2026-44479? CVE-2026-44479 is a medium-severity security vulnerability in vercel (npm), affecting versions >= 50.16.0, <= 52.0.0. It is fixed in 52.0.1.
2. How severe is CVE-2026-44479? CVE-2026-44479 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of vercel are affected by CVE-2026-44479? vercel (npm) versions >= 50.16.0, <= 52.0.0 is affected.
4. Is there a fix for CVE-2026-44479? Yes. CVE-2026-44479 is fixed in 52.0.1. Upgrade to this version or later.
5. Is CVE-2026-44479 exploitable, and should I be worried? Whether CVE-2026-44479 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-44479 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-44479? Upgrade vercel to 52.0.1 or later.