CVE-2026-87723: Untrusted Search Path (PATH Hijacking) in fuse-archive
In Google fuse-archive versions prior to 1.24, an attacker who can prepend a directory to PATH or write a malicious binary to an attacker-controlled or writable directory appearing in PATH can hijack the execution pathway. This allows the attacker to execute arbitrary local code under the security context of the user running the fuse-archive process. The issue was partially mitigated in version 1.22 and fully resolved in 1.24 via refined selective PATH filtering.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google fuse-archiveto a version that resolves this vulnerability.Fixed in 1.24
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Google fuse-archive versions before 1.24 are affected. Version 1.22 includes a partial mitigation, while 1.24 fully resolves the issue through selective PATH filtering.
What access does an attacker need to exploit it?
The attacker must be able to prepend a directory to the PATH environment variable or place a malicious executable in an attacker-controlled or writable directory that appears in PATH. Successful exploitation results in local code execution as the user running fuse-archive.
What can be done if an immediate upgrade is not possible?
Prevent untrusted directories from being added to PATH and ensure that directories included in PATH are not writable by untrusted users. This removes the conditions needed to substitute a malicious binary into fuse-archive's execution path.