CVE-2026-73505 JanDeDobbeleer CVE debrief

Who should care

Defenders responsible for Oh My Posh deployments, particularly in environments where user-controlled directory names are possible, should assess exposure and prioritize upgrading to version 29.35.1 or later.

Why it matters

CVE-2026-73505 is a high-severity vulnerability in Oh My Posh that allows arbitrary OS command execution via attacker-controlled directory names. Defenders should prioritize verifying and upgrading to version 29.35.1 or later, assessing exposure, and monitoring for potential exploitation attempts.

• Potential for arbitrary OS command execution as the current user
• Need for verification of exposure in environments using Oh My Posh
• Priority for upgrading to version 29.35.1 or later
• Monitoring for potential exploitation attempts

Technical summary

The setStyle() function in src/segments/path.go passed pt.Path, which includes raw folder names, to template.Render, whose function map exposes cmd, allowing an attacker-controlled directory name containing a Go template expression to execute arbitrary operating system commands as the current user. This vulnerability, CVE-2026-73505, is a high-severity issue in Oh My Posh, a customizable and low-latency cross-platform/shell prompt renderer. An attacker-controlled directory name containing a Go template expression could execute arbitrary operating system commands as the current user when the prompt is rendered inside that directory or a descendant. The issue is fixed in version 29.35.1.

Defensive priority

Defenders should prioritize verifying and upgrading to version 29.35.1 or later, assessing exposure in their environments, and monitoring for potential exploitation attempts.

Recommended defensive actions

• Verify and upgrade to version 29.35.1 or later
• Assess exposure in environments using Oh My Posh
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided information, requiring verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.