Information Disclosure in vercel (CVE-2026-44479)
Summary
Vulnerability in vercel (CVE-2026-44479). Confidential information can be exposed externally. Exploitable via VERCEL_TOKEN. Mitigation: upgrade to 52.0.1 or later.
Original description
The description as published by the source.
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:
- Token passed as a CLI argument (
--token/-t). TheVERCEL_TOKENenvironment variable is not affected. - Non-interactive mode is active (explicit flag or AI agent auto-detection).
- 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
--tokenwith--non-interactivein their applications, review logs for exposed tokens and rotate them. - Prefer
VERCEL_TOKENenvironment variable for authentication.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44479 has been found in vercel.
Attackers can target a specific entry point like VERCEL_TOKEN over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade vercel to 52.0.1 or later.
If unsure, ask your IT team or search "vercel CVE-2026-44479" on the vendor's site.
CVE-2026-44479 (vercel) — CWE-200 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: VERCEL_TOKEN
Patched: 52.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in vercel. Attackers reach the vulnerable code path via VERCEL_TOKEN without authentication.
Check the vendor advisory for the affected versions of vercel. Attack surface: VERCEL_TOKEN.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 52.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vercel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vercel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vercelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade vercel to 52.0.1ステージング環境で 52.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch security-advisories@github.com
- web github.com