LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47091: Claude HUD 0.0.12 Path Traversal via transcript_path

Claude HUD through 0.0.12, patched in commit 234d9aa, contains a path traversal vulnerability that allows attackers to read arbitrary files by supplying an unvalidated transcript_path value via stdin JSON. Attackers can access any file readable by the process and the file metadata is written to a persistent cache file with insufficient permissions, creating a forensic record of accessed paths that survives process exit.

MediumCVSS 4.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Claude HUD through 0.0.12 can be tricked into reading files outside the intended transcript location when given a malicious transcript_path value. The impact is mainly confidential file exposure, limited to files the Claude HUD process can already read. The sources do not show active exploitation.

Executive priority

Treat this as a moderate workstation and developer-tool risk. Prioritize remediation where Claude HUD runs near secrets, source code, credentials, or shared user environments. It is not evidenced as remotely exploitable or actively exploited in the provided sources.

Technical view

CVE-2026-47091 is a CWE-22 path traversal in claude-hud via unvalidated transcript_path supplied through stdin JSON. The CVSS 4.0 score is 4.8: local attack vector, low complexity, low privileges, no user interaction, low confidentiality impact, and no stated integrity or availability impact. A patch is identified at commit 234d9aa.

Likely exposure

Exposure is most likely on developer or workstation environments running claude-hud through 0.0.12, especially where untrusted or semi-trusted local users, scripts, or integrations can supply stdin JSON to the process.

Exploitation context

The source bundle does not identify known exploitation, and KEV is false. Exploitation requires local access or equivalent ability to influence Claude HUD stdin JSON. Successful abuse can disclose files readable by the process and leave accessed-path metadata in a persistent cache.

Researcher notes

The important constraints are local attack vector, required low privileges, transcript_path input through stdin JSON, arbitrary file read within process permissions, and persistent cache metadata with insufficient permissions. Sources identify the patch commit but do not provide a versioned fixed release in the bundle.

Mitigation direction

  • Update to code containing commit 234d9aa or later vendor guidance.
  • Stop using claude-hud through 0.0.12 where untrusted local input is possible.
  • Run Claude HUD with least-privilege file access.
  • Restrict who can invoke integrations that pass stdin JSON.
  • Review vendor guidance for any release-specific upgrade path.

Validation and detection

  • Inventory systems and developer workstations running claude-hud.
  • Confirm deployed code includes patch commit 234d9aa or an equivalent fix.
  • Review whether stdin JSON can be influenced by untrusted users or tools.
  • Check cache-file permissions and retained metadata for unexpected accessed paths.
  • Verify the process cannot read sensitive files unrelated to Claude HUD.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47091 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheck
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N1.81.4VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

4.8Medium
CVSS 4.0 vector shape for CVE-2026-47091Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
jarrodwattsclaude-hud0, 234d9aad919b51326a43bcf90b45ae35c23afc30affected
Weakness

CWE details

CWE-22

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs