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

> Vercel CLI leaks authentication tokens in command suggestions during non-interactive runs, exposing credentials in logs.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-pgf8-2hgj-grqg

## What is CVE-2026-44479?

CVE-2026-44479 is a medium-severity vulnerability in vercel, published on 13 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-44479?

2 open source packages ship an affected version, including vercel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vercel` | npm | From 50.16.0 | 52.0.1 |
| `vercel` | npm | From 50.16.0 | 52.0.1 |

Products: Vercel Vercel.

## How do I fix CVE-2026-44479?

Upgrade vercel to 52.0.1 or later.

## Is CVE-2026-44479 being exploited?

There is no known exploitation of CVE-2026-44479 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44479 and fix it if it is affected.

What it is: CVE-2026-44479 is a medium-severity vulnerability in vercel, published on 13 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44479 in the wild and no public exploit code.

Affected packages and fixed versions:
- vercel (npm): affected from 50.16.0; fixed in 52.0.1
- vercel (npm): affected from 50.16.0; fixed in 52.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44479/ (Markdown: https://insights.sbomify.com/CVE-2026-44479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44479
- OSV: https://osv.dev/vulnerability/CVE-2026-44479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44479/
Summaries are generated and may contain mistakes; the official description above is the record.