{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54686 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54686 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54686 is a medium-severity vulnerability in warpdotdev warp, published on 24 Jun 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-54686 and fix it if it is affected.\n\nWhat it is: CVE-2026-54686 is a medium-severity vulnerability in warpdotdev warp, published on 24 Jun 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-54686 in the wild and no public exploit code.\n\nAffected product: warpdotdev warp. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-54686/ (Markdown: https://insights.sbomify.com/CVE-2026-54686/index.md)","id":"CVE-2026-54686","markdown":"https://insights.sbomify.com/CVE-2026-54686/index.md","name":"CVE-2026-54686","record":{"aliases":["GHSA-9w2v-jhww-vm85"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Warp terminal","requires_auth":"none","summary":"Attackers can spoof terminal lifecycle hooks to alter session metadata like working directory or SSH transport details in Warp.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Warp is an agentic development environment. From 0.2021.04.25.23.05.stable_00 until 0.2026.05.06.15.42.stable_01, Warp accepted certain state-mutating terminal lifecycle hooks from the PTY stream without verifying that the hooks were emitted by Warp's shell integration for the active session. An attacker who could cause a victim to view attacker-controlled terminal output in Warp could spoof selected lifecycle metadata, including the current working directory reported for the active block or SSH session transport metadata. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-16T04:41:10Z","kind":"github_poc","ref":"https://github.com/Saku0512/CVE-2026-54686-poc","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"Warp: DCS lifecycle hook spoofing can alter terminal session metadata","id":"CVE-2026-54686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"n8n-nodes-sqlite3: Path traversal via user-controlled database file path (db_path parameter)","id":"CVE-2026-54687"},"packages":[],"prev":{"headline":"FileBrowser Quantum has Username Enumeration via Authentication Timing Side-Channel","id":"CVE-2026-54685"},"products":["warp"],"published":"2026-06-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["warpdotdev"]},"summary":"Attackers can spoof terminal lifecycle hooks to alter session metadata like working directory or SSH transport details in Warp.","url":"https://insights.sbomify.com/CVE-2026-54686/"}