Local file disclosure via unvalidated transcript path
Published May 18, 2026 · Updated May 18, 2026
Path traversal in Claude HUD 0.0.12 and earlier allows local users to read any process-readable file through stdin JSON transcript_path. parseTranscript uses the supplied path for filesystem stat and stream operations without a directory-boundary check, then persists file metadata in a cache. Exploitation requires control of JSON delivered to the local statusline process; ordinary Claude Code transcript paths remain in transcript storage.
Summary
What happened
Path traversal in Claude HUD 0.0.12 and earlier allows local users to read any process-readable file through stdin JSON transcript_path. parseTranscript uses the supplied path for filesystem stat and stream operations without a directory-boundary check, then persists file metadata in a cache. Exploitation requires control of JSON delivered to the local statusline process; ordinary Claude Code transcript paths remain in transcript storage.
The record
- CVE
- CVE-2026-47091
- Published
- May 18, 2026
- Updated
- May 18, 2026
- Vendor
- Jarrod Watts
- Product
- Claude HUD
- Classifications
- CWE-22, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 2026CVE publishedPublication date reported by the CVE source.
- May 18, 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 <=0.0.12
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo