Description
Warp versions before the patched release 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.
Impact
Successful exploitation of the scoped CWD issue may cause Warp to treat an attacker-chosen path as the active session's current working directory. This can affect Warp features that seed path, context, or session behavior from the active CWD.
Patch
The patch adds client-generated session IDs for Warp lifecycle hooks and rejects state-mutating hooks whose session IDs are missing or not registered for the session.
Workarounds
No complete workaround is available other than updating.
Credits
Thanks to the following reporter who responsibly disclosed this issue:
References
Description
Warp versions before the patched release 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.
Impact
Successful exploitation of the scoped CWD issue may cause Warp to treat an attacker-chosen path as the active session's current working directory. This can affect Warp features that seed path, context, or session behavior from the active CWD.
Patch
The patch adds client-generated session IDs for Warp lifecycle hooks and rejects state-mutating hooks whose session IDs are missing or not registered for the session.
Workarounds
No complete workaround is available other than updating.
Credits
Thanks to the following reporter who responsibly disclosed this issue:
References
v0.2026.05.06.15.42.stable_01