Approved changes feed: RSS · Atom
cpe:2.3:a:vercel:vercel:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Vercel (5676cb1a-0d7f-5c57-9405-b569f0c482e7) |
|---|---|
| Product | Vercel (ffa61748-bccf-58ee-8aac-d32466a14cb8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/vercel/vercel |
purl2cpe | 2026-06-01 10:11:38.507330 |
pkg:npm/vercel |
purl2cpe | 2026-06-01 10:11:38.507332 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-44479 |
vulnerable | 2026-06-08 08:05:11.104193 |
Vercel: Non-interactive mode includes CLI arguments in suggested command output
MEDIUM (5.5)
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.
Published: 2026-05-13T15:36:36.764Z
Updated: 2026-05-13T18:19:54.986Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-49005 |
vulnerable | 2026-06-08 07:29:12.461023 |
Next.js cache poisoning due to omission of Vary header
LOW (3.7)
Next.js is a React framework for building full-stack web applications. In Next.js App Router from 15.3.0 to before 15.3.3 and Vercel CLI from 41.4.1 to 42.2.0, a cache poisoning vulnerability was found. The issue allowed page requests for HTML content to return a React Server Component (RSC) payload instead under certain conditions. When deployed to Vercel, this would only impact the browser cache, and would not lead to the CDN being poisoned. When self-hosted and deployed externally, this could lead to cache poisoning if the CDN does not properly distinguish between RSC / HTML in the cache keys. This issue has been resolved in Next.js 15.3.3.
Published: 2025-07-03T21:01:14.743Z
Updated: 2025-07-08T14:34:12.642Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.