Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73506 medium CVSS 6.1

Vulnerability in github.com/jandedobbeleer/oh-my-posh (CVE-2026-73506)

Summary

Vulnerability in github.com/jandedobbeleer/oh-my-posh (CVE-2026-73506). Risk of unauthorized operations or information disclosure. Exploitable via formats.EscapeSequences. Mitigation: upgrade to 29.35.1 or later.

Original description

The description as published by the source.

Summary

Oh My Posh renders dynamic, potentially attacker-controlled strings (the current directory name, Git commit metadata, environment variable values, command output) into the prompt without neutralizing raw terminal control characters. An attacker who controls one of these values can inject ANSI/OSC escape sequences that the victim's terminal executes on every prompt render. (This is separate from the path-segment command-execution report; it has a different root cause and fix.)

Details

src/terminal/writer.go, write(s rune): the literal characters of rendered segment content are emitted to the output buffer, and the only neutralization is a lookup in formats.EscapeSequences, which per shell contains only the shell's prompt-length markers (\ for bash, % for zsh, nothing for fish/pwsh/cmd/nu). Raw C0/C1 control bytes (ESC 0x1b, BEL 0x07, CSI, OSC) are written verbatim.

Oh My Posh's own styling is emitted through separate paths (writeEscapedAnsiString, writeColorise, builder.WriteString(formats.Hyperlink...)), so any control rune reaching write(s rune) originates from rendered data. trimAnsi is already applied to the console title (FormatTitle) but not to the prompt body.

Attacker-controlled sources (both verified)

  1. Current directory name (default config, Linux/macOS). Directory names may contain any byte except / and NUL, including 0x1b. The path segment renders the working directory in every theme.
  2. Git commit subject / aut…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73506 has been found in github.com/jandedobbeleer/oh-my-posh.
Attackers can target a specific entry point like formats.EscapeSequences over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade github.com/jandedobbeleer/oh-my-posh to 29.35.1 or later.
If unsure, ask your IT team or search "github.com/jandedobbeleer/oh-my-posh CVE-2026-73506" on the vendor's site.

CVE-2026-73506 (github.com/jandedobbeleer/oh-my-posh) — CWE-150 / CVSS v3 6.1
Attack vector: local / unauthenticated
Attack surface: formats.EscapeSequences / writeEscapedAnsiString / writeColorise / trimAnsi
Patched: 29.35.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-150) exists in github.com/jandedobbeleer/oh-my-posh. Attackers reach the vulnerable code path via formats.EscapeSequences without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/jandedobbeleer/oh-my-posh. Attack surface: formats.EscapeSequences / writeEscapedAnsiString / writeColorise / trimAnsi.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 29.35.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/jandedobbeleer/oh-my-posh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/jandedobbeleer/oh-my-posh' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/jandedobbeleer/oh-my-posh を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/jandedobbeleer/oh-my-posh to 29.35.1

    ステージング環境で 29.35.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/jandedobbeleer/oh-my-posh
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"29.35.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details