{"answers":{"affected":"2 open source packages ship an affected version, including vercel. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44479 in the wild and no public exploit code.","fix":"Upgrade vercel to 52.0.1 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-44479 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-44479 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vercel (npm): affected from 50.16.0; fixed in 52.0.1\n- vercel (npm): affected from 50.16.0; fixed in 52.0.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44479/ (Markdown: https://insights.sbomify.com/CVE-2026-44479/index.md)","id":"CVE-2026-44479","markdown":"https://insights.sbomify.com/CVE-2026-44479/index.md","name":"CVE-2026-44479","record":{"aliases":["GHSA-pgf8-2hgj-grqg"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vercel CLI","requires_auth":"none","summary":"Vercel CLI leaks authentication tokens in command suggestions during non-interactive runs, exposing credentials in logs.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vercel","vendor":"vercel"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Vercel: Non-interactive mode includes CLI arguments in suggested command output","id":"CVE-2026-44479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"soundcloud-rpc: Remote Code Execution via XSS in Track Title","id":"CVE-2026-44482"},"packages":[{"ecosystem":"npm","fixed":["52.0.1"],"introduced":["50.16.0"],"last_affected":[],"package":"vercel","purl":null,"source":"GHSA-pgf8-2hgj-grqg"},{"ecosystem":"npm","fixed":["52.0.1"],"introduced":["50.16.0"],"last_affected":[],"package":"vercel","purl":"pkg:npm/vercel","source":"GHSA-pgf8-2hgj-grqg"}],"prev":{"headline":"hoppscotch: Unauthenticated Onboarding Config Disclosure via Empty Recovery Token","id":"CVE-2026-44478"},"products":["vercel"],"published":"2026-05-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["vercel"]},"summary":"Vercel CLI leaks authentication tokens in command suggestions during non-interactive runs, exposing credentials in logs.","url":"https://insights.sbomify.com/CVE-2026-44479/"}