{"answers":{"affected":"2 open source packages ship an affected version, including turbo. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45773 in the wild and no public exploit code.","fix":"Upgrade turbo to 2.9.14 or later.","what":"CVE-2026-45773 is a medium-severity vulnerability in vercel turborepo, published on 15 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-45773 and fix it if it is affected.\n\nWhat it is: CVE-2026-45773 is a medium-severity vulnerability in vercel turborepo, published on 15 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-45773 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- turbo (npm): affected all versions; fixed in 2.9.14\n- turbo (npm): affected all versions; fixed in 2.9.14\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-45773/ (Markdown: https://insights.sbomify.com/CVE-2026-45773/index.md)","id":"CVE-2026-45773","markdown":"https://insights.sbomify.com/CVE-2026-45773/index.md","name":"CVE-2026-45773","record":{"aliases":["GHSA-hcf7-66rw-9f5r","MINI-8vcx-qj7x-vf4c"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Turborepo CLI","requires_auth":"none","summary":"Attackers can hijack Turborepo CLI login sessions via CSRF on self-hosted auth flows, allowing unauthorized access to build caches.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"turborepo","vendor":"vercel"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-384","name":"Session Fixation"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Turborepo is a high-performance build system for JavaScript and TypeScript codebases. Prior to 2.9.14, Turborepo's self-hosted login and SSO browser flows did not validate a CSRF state value on the localhost callback. While the CLI was waiting for authentication, a malicious web page could send a request to the local callback server with an attacker-controlled token. If accepted before the legitimate callback, the CLI could complete login with the wrong credentials. This affects users authenticating the turbo CLI against self-hosted remote cache/auth endpoints. Vercel-hosted login flows using device authorization are not affected. This vulnerability is fixed in 2.9.14.","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":"Turborepo: Login callback CSRF/session fixation","id":"CVE-2026-45773","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"compliance-trestle Profile Import has an Arbitrary File Read via trestle:// URI and Relative Path Traversal","id":"CVE-2026-45774"},"packages":[{"ecosystem":"npm","fixed":["2.9.14"],"introduced":["0"],"last_affected":[],"package":"turbo","purl":null,"source":"GHSA-hcf7-66rw-9f5r"},{"ecosystem":"npm","fixed":["2.9.14"],"introduced":["0"],"last_affected":[],"package":"turbo","purl":"pkg:npm/turbo","source":"GHSA-hcf7-66rw-9f5r"}],"prev":{"headline":"Turborepo: Unexpected local code execution during Yarn Berry detection","id":"CVE-2026-45772"},"products":["turborepo"],"published":"2026-05-15","related":[{"cvss_score":0,"headline":"Turborepo: Unexpected local code execution during Yarn Berry detection","id":"CVE-2026-45772","kev_date_added":null,"published":"2026-05-15"}],"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-15","vendors":["vercel"]},"summary":"Attackers can hijack Turborepo CLI login sessions via CSRF on self-hosted auth flows, allowing unauthorized access to build caches.","url":"https://insights.sbomify.com/CVE-2026-45773/"}