https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-10-04T18:42:19.199759+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/brew-vercel-cve-2026-44479 BREW-vercel-CVE-2026-44479 — Vercel: Non-interactive mode includes CLI arguments in suggested command output 2026-10-04T18:42:19.201937+00:00

Affected: Homebrew: vercel

# 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 `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.

## 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 `VERCEL_TOKEN` environment variable for authentication.

 https://db.gcve.eu/vuln/cve-2026-44479 CVE-2026-44479 — Vercel: Non-interactive mode includes CLI arguments in suggested command output 2026-10-04T18:42:19.202065+00:00

Affected: vercel

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.