CVE-2026-50158

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

yutu is an AI-powered toolkit for managing and growing YouTube channels. Prior to 0.10.9, the caption-download MCP tool accepts a caller-controlled file parameter through cmd/caption/download.go and passes it to Caption.Download() in pkg/caption/caption.go, where os.Create() creates or truncates that path without using the pkg.Root confinement boundary backed by YUTU_ROOT. A principal able to invoke caption-download, including a local HTTP client when the MCP server runs with its default authentication-disabled configuration, can write downloaded caption bytes to any path writable by the yutu process outside YUTU_ROOT. This can overwrite application files, configuration, shell startup files, logs, or data and can cause persistent code execution or denial of service depending on the selected writable target. Live caption retrieval also requires usable service credentials and an accessible caption identifier. This issue is fixed in version 0.10.9.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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
12th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (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.

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 14, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v0.10.9

Patch available: eat-pray-ai/yutu v0.10.9

https://github.com/eat-pray-ai/yutu/releases/tag/v0.10.9
GitHub commit

commit 87026c4eee1e (eat-pray-ai/yutu)

Fix landed in eat-pray-ai/yutu commit 87026c4eee1e — awaiting tagged release

https://github.com/eat-pray-ai/yutu/commit/87026c4eee1ed28775383807087343a750707bf3
GitHub advisoryMentions a patch (unverified)

Arbitrary File Write via MCP `caption-download` Tool · Advisory · eat-pray-ai/yutu · GitHub

https://github.com/eat-pray-ai/yutu/security/advisories/GHSA-2c7f-fxww-6w6c

Vendor Advisories for CVE-2026-50158(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/eat-pray-ai/yutu—
  • every version up to 0.10.9-dev1: fixed in 0.10.9-dev1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 33× 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.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-01 12:53 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-09-28 08:54 UTCEG score recompute
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-09-24 21:40 UTCEG score recompute
Show 12 more
  1. 2026-09-24 09:01 UTCEG score recompute
  2. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-09-23 03:29 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-09-18 15:27 UTCEG score recompute
  7. 2026-09-18 14:54 UTCEG score recompute
  8. 2026-09-17 22:25 UTCEG score recompute
  9. 2026-07-30 14:55 UTCEG score recompute
  10. 2026-07-26 11:43 UTCEG score recompute
  11. 2026-07-23 03:18 UTCEG score recompute
  12. 2026-07-14 19:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50158?
CVE-2026-50158 is a high-severity vulnerability; its CVE record was published on July 14, 2026. yutu is an AI-powered toolkit for managing and growing YouTube channels. Prior to 0.10.9, the caption-download MCP tool accepts a caller-controlled file parameter through cmd/caption/download.go and passes it to Caption.Download() in pkg/caption/caption.go, where os.Create() creates or truncates…
When was the CVE record for CVE-2026-50158 published?
The CVE record for CVE-2026-50158 was published on July 14, 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 September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-50158 actively exploited?
CVE-2026-50158 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50158?
CVE-2026-50158 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50158?
A fix for CVE-2026-50158 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50158 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-50158

Explore →

Is Your Infrastructure Affected by CVE-2026-50158?

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

Book a Demo →Browse All CVEs