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

Published May 7, 2026
·
Updated

Summary

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 rotate them. - Prefer VERCELTOKEN environment variable for authentication.

Other sources

Vercel’s AI Cloud is a unified platform for building modern applications. From 50.16.0 to 52.0.0, hen 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. The plaintext token may be captured in CI/CD logs, agent transcripts, or other automation output. This vulnerability is fixed in 52.0.1.

MITRE

Affected Software

2 affected componentsFixes available
npm/vercel>=50.16.0<=52.0.0
52.0.1
Vercel Vercel Node.js>=50.16.0<52.0.1

Event History

May 7, 2026
Advisory Published
via GitHub·12:05 AM
Data Sourced
via GitHub·12:05 AM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·03:36 PM
Data Sourced
via MITRE·03:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44479?

The severity of CVE-2026-44479 is currently classified as moderate due to the potential exposure of sensitive token data.

2

How do I fix CVE-2026-44479?

To fix CVE-2026-44479, upgrade the vercel package to version 52.0.1 or higher.

3

What software is affected by CVE-2026-44479?

CVE-2026-44479 affects the vercel package versions between 50.16.0 and 52.0.0 on npm.

4

What are the risks associated with CVE-2026-44479?

The risks associated with CVE-2026-44479 include potential leakage of sensitive token values in JSON payloads when using non-interactive commands.

5

Is authentication with the token secure in scenarios affected by CVE-2026-44479?

Authentication with the token is not secure in the affected scenarios, as the token value may be exposed in output payloads.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203