CVE-2026-73506

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.1 from GitHub Security Advisory (severity: MODERATE) published 2026-07-24. A secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-58081 (ENISA EUVD) · GHSA-fwjx-9p69-h25h (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Oh My Posh is the most customisable and low-latency cross platform/shell prompt renderer. Prior to 29.35.1, write(s rune) in src/terminal/writer.go emitted attacker-controlled current directory names and Git metadata, including Commit.Subject, Commit.Author.Name, Commit.Author.Email, and RawUpstreamURL, without removing C0/C1 terminal control characters such as ESC, BEL, CSI, and OSC, allowing terminal escape sequence injection during prompt rendering that could overwrite the clipboard, spoof the prompt or screen, manipulate the window title, or disrupt the terminal. This issue is fixed in version 29.35.1.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 24, 2026

Last Modified

October 24, 2026

Advisory Details (4)

Auto-updated Aug 13, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

Terminal escape sequence injection via unsanitized prompt segment data · Advisory · JanDeDobbeleer/oh-my-posh · GitHub

https://github.com/JanDeDobbeleer/oh-my-posh/security/advisories/GHSA-fwjx-9p69-h25h
GitHub release Patch Available

v29.35.1

Patch available: JanDeDobbeleer/oh-my-posh v29.35.1

https://github.com/JanDeDobbeleer/oh-my-posh/releases/tag/v29.35.1
GitHub pull request

next

Fix merged in JanDeDobbeleer/oh-my-posh PR #7711 on 2026-07-23 — awaiting tagged release

https://github.com/JanDeDobbeleer/oh-my-posh/pull/7711
GitHub commit

commit edcf3c88f3fb (JanDeDobbeleer/oh-my-posh)

Fix landed in JanDeDobbeleer/oh-my-posh commit edcf3c88f3fb — awaiting tagged release

https://github.com/JanDeDobbeleer/oh-my-posh/commit/edcf3c88f3fb582e84358b385c49d33d04c04224

Vendor Advisories for CVE-2026-73506(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/jandedobbeleer/oh-my-posh @ 29.35.1 (fixes <= 29.35.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/jandedobbeleer/oh-my-posh—
  • every version up to 29.35.1: fixed in 29.35.1
  • every version up to 29.35.1+incompatible: fixed in 29.35.1+incompatible
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 115 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-11-01 07:39 UTCGHSA enrichmentGHSA-fwjx-9p69-h25h · GitHub severity MODERATE · GitHub CVSS 6.1
  3. 2026-11-01 07:39 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-25 14:05 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-23 18:26 UTCEG score recompute
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-22 19:01 UTCEG score recompute
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-18 03:15 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 73 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 15:40 UTCEG score recompute
  4. 2026-10-11 19:26 UTCEG score recompute
  5. 2026-10-11 16:42 UTCEG score recompute
  6. 2026-10-11 14:01 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-04 07:41 UTCEG score recompute
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-02 19:42 UTCEG score recompute
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-01 04:31 UTCEG score recompute
  20. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-28 04:25 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-25 09:59 UTCEG score recompute
  26. 2026-09-23 22:32 UTCEG score recompute
  27. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-22 22:09 UTCEG score recompute
  29. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-20 01:39 UTCEG score recompute
  32. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-18 02:56 UTCEG score recompute
  34. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-16 11:58 UTCEG score recompute
  36. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-09-15 09:34 UTCEG score recompute
  38. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-14 03:43 UTCEG score recompute
  40. 2026-09-13 03:19 UTCEG score recompute
  41. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-09-12 02:55 UTCEG score recompute
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  44. 2026-09-11 02:30 UTCEG score recompute
  45. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-09-09 08:43 UTCEG score recompute
  47. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-07 21:23 UTCEG score recompute
  49. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-09-05 19:22 UTCEG score recompute
  51. 2026-09-04 12:44 UTCEG score recompute
  52. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-09-01 23:15 UTCEG score recompute
  55. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-08-31 00:38 UTCEG score recompute
  58. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-08-30 00:14 UTCEG score recompute
  61. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  62. 2026-08-28 01:29 UTCEG score recompute
  63. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  64. 2026-08-27 01:05 UTCEG score recompute
  65. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  66. 2026-08-26 00:38 UTCEG score recompute
  67. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  68. 2026-08-24 23:48 UTCEG score recompute
  69. 2026-08-23 23:23 UTCEG score recompute
  70. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-08-22 22:59 UTCEG score recompute
  72. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  73. 2026-08-21 22:35 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-73506?
CVE-2026-73506 is a medium-severity vulnerability; its CVE record was published on July 24, 2026. Oh My Posh is the most customisable and low-latency cross platform/shell prompt renderer. Prior to 29.35.1, write(s rune) in src/terminal/writer.go emitted attacker-controlled current directory names and Git metadata, including Commit.Subject, Commit.Author.Name, Commit.Author.Email, and…
When was the CVE record for CVE-2026-73506 published?
The CVE record for CVE-2026-73506 was published on July 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73506 actively exploited?
CVE-2026-73506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73506?
CVE-2026-73506 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73506?
A fix for CVE-2026-73506 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73506 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73506

Explore →

Is Your Infrastructure Affected by CVE-2026-73506?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.