{"answers":{"affected":"4 open source packages ship an affected version, including ai. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48985 in the wild and no public exploit code.","fix":"Upgrade ai to a fixed version for your release line: 5.0.52 or 5.1.0-beta.9.","what":"CVE-2025-48985 is a low-severity vulnerability in Vercel AI SDK, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48985 and fix it if it is affected.\n\nWhat it is: CVE-2025-48985 is a low-severity vulnerability in Vercel AI SDK, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48985 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ai (npm): affected all versions; fixed in 5.0.52\n- ai (npm): affected all versions; fixed in 5.0.52\n- ai (npm): affected from 5.1.0-beta.0; fixed in 5.1.0-beta.9\n- ai (npm): affected from 5.1.0-beta.0; fixed in 5.1.0-beta.9\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-2025-48985/ (Markdown: https://insights.sbomify.com/CVE-2025-48985/index.md)","id":"CVE-2025-48985","markdown":"https://insights.sbomify.com/CVE-2025-48985/index.md","name":"CVE-2025-48985","record":{"aliases":["ECHO-9790-2fa3-84e4","GHSA-rwvc-j5jr-mgvh","MINI-2f7x-49qg-3j3j","MINI-3gx6-g372-w7fr","MINI-7hx3-hxfm-3jg5","MINI-f35c-w682-rr9c","MINI-j35r-rhv7-7cx6","MINI-m3q6-gm92-wqrm","MINI-qr5f-fjr4-ccfj","MINI-x8mx-qfff-gcjc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vercel AI SDK","requires_auth":"none","summary":"Attackers can bypass filetype whitelists during file uploads in the Vercel AI SDK, potentially allowing malicious file execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"ai","vendor":"vercel"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A vulnerability in Vercel’s AI SDK has been fixed in versions 5.0.52, 5.1.0-beta.9, and 6.0.0-beta. This issue may have allowed users to bypass filetype whitelists when uploading files. All users are encouraged to upgrade.\r\n\r\nMore details: https://vercel.com/changelog/cve-2025-48985-input-validation-bypass-on-ai-sdk","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’s AI SDK's filetype whitelists can be bypassed when uploading files","id":"CVE-2025-48985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":4,"n_references":2,"next":{"headline":"Missing authorization in Revive Adserver","id":"CVE-2025-48986"},"packages":[{"ecosystem":"npm","fixed":["5.0.52"],"introduced":["0"],"last_affected":[],"package":"ai","purl":null,"source":"GHSA-rwvc-j5jr-mgvh"},{"ecosystem":"npm","fixed":["5.0.52"],"introduced":["0"],"last_affected":[],"package":"ai","purl":"pkg:npm/ai","source":"GHSA-rwvc-j5jr-mgvh"},{"ecosystem":"npm","fixed":["5.1.0-beta.9"],"introduced":["5.1.0-beta.0"],"last_affected":[],"package":"ai","purl":null,"source":"GHSA-rwvc-j5jr-mgvh"},{"ecosystem":"npm","fixed":["5.1.0-beta.9"],"introduced":["5.1.0-beta.0"],"last_affected":[],"package":"ai","purl":"pkg:npm/ai","source":"GHSA-rwvc-j5jr-mgvh"}],"prev":{"headline":"Code injection in Backup and Replication","id":"CVE-2025-48984"},"products":["AI SDK"],"published":"2025-11-07","related":[{"cvss_score":6.9,"headline":"vercel ai provider-utils download-blob.ts validateDownloadUrl server-side request forgery","id":"CVE-2026-8768","kev_date_added":null,"published":"2026-05-17"},{"cvss_score":5.3,"headline":"vercel ai provider-utils response-handler.ts createJsonErrorResponseHandler resource consumption","id":"CVE-2026-8769","kev_date_added":null,"published":"2026-05-17"},{"cvss_score":2.3,"headline":"vercel ai PR Branch Name Interpolation prettier-on-automerge.yml run os command injection","id":"CVE-2026-8767","kev_date_added":null,"published":"2026-05-17"}],"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":"2025-12-01","vendors":["Vercel"]},"summary":"Attackers can bypass filetype whitelists during file uploads in the Vercel AI SDK, potentially allowing malicious file execution.","url":"https://insights.sbomify.com/CVE-2025-48985/"}