Local code execution via unsafe helper search path
Published Sep 28, 2026 · Updated Sep 28, 2026
PATH hijacking in Google fuse-archive before 1.24 allows local users to execute code as the mounting user through external filter helpers. During archive bidding, decompression, or filter setup, helper names can be resolved through PATH entries that are not adequately restricted against attacker-controlled binaries. Exploitation requires control of a directory on the helper search path and execution of an external helper during an archive mount.
Summary
What happened
PATH hijacking in Google fuse-archive before 1.24 allows local users to execute code as the mounting user through external filter helpers. During archive bidding, decompression, or filter setup, helper names can be resolved through PATH entries that are not adequately restricted against attacker-controlled binaries. Exploitation requires control of a directory on the helper search path and execution of an external helper during an archive mount.
The record
- CVE
- CVE-2026-87723
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- WebM Project
- Product
- fuse-archive
- Classifications
- T1574.007
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started