{"answers":{"affected":"1 open source package ship an affected version, including bun.","exploited":"There is no known exploitation of CVE-2025-8022 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8022 is a vulnerability in bun, published on 23 Jul 2025."},"fix_prompt":"Check this codebase for CVE-2025-8022 and fix it if it is affected.\n\nWhat it is: CVE-2025-8022 is a vulnerability in bun, published on 23 Jul 2025. \nExploitation: There is no known exploitation of CVE-2025-8022 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bun (npm): affected all versions up to 1.1.39; no fix listed\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-8022/ (Markdown: https://insights.sbomify.com/CVE-2025-8022/index.md)","id":"CVE-2025-8022","markdown":"https://insights.sbomify.com/CVE-2025-8022/index.md","name":"CVE-2025-8022","record":{"aliases":["GHSA-4j66-8f4r-3pjx"],"analysis":null,"analysis_generated_by":null,"assigner":"snyk","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Bun Shell does not invoke /bin/sh, or any other interpreter, for template literals created with the $ function. Each ${…} interpolation is treated as a single argument. The security responsibility for this usage pattern lies with the calling application, which must ensure the sanitization and validation of any untrusted arguments before passing them to the executed commands. Therefore, the potential for command injection is not a flaw within Bun itself; rather, it is an argument injection that is contingent on its implementation by the consuming application.","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":false,"headline":"Bun Shell does not invoke /bin/sh, or any other interpreter, for template literals created with the $ function.","id":"CVE-2025-8022","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2025"},"n_packages":1,"n_references":0,"next":{"headline":"Path Traversal in Template Upload Allows Uploading Files Outside Target Directory","id":"CVE-2025-8023"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.39"],"package":"bun","purl":"pkg:npm/bun","source":"GHSA-4j66-8f4r-3pjx"}],"prev":{"headline":"files-bucket-server vulnerable to Directory Traversal","id":"CVE-2025-8021"},"products":[],"published":"2025-07-23","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"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2025-08-11","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-8022/"}