CVE-2025-68119

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-01-28. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

January 28, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

GO-2026-4338 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4338
generic
https://groups.google.com/g/golang-announce/c/Vd2tYVM8eUc
generic

cmd/go: unexpected code execution when invoking toolchain (CVE-2025-68119) · Issue #77099 · golang/go · GitHub

https://go.dev/issue/77099
generic
https://go.dev/cl/736710

Vendor Advisories for CVE-2025-68119(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgolang1-25-main-1.25.9-1.hum12026-04-10redhat
redhatgolang1-26-main-1.26.2-1.hum12026-04-09redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-1.251.25.0-1, 1.25.0-2, 1.25.1-1, 1.25.2-1, 1.25.3-11.25.6-1—
Go(1)
PackageVulnerable rangeFixed inDependents
toolchain—1.25.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-08-31 21:34 UTCOSV refresh
  5. 2026-08-30 01:21 UTCEPSS rescore
  6. 2026-08-28 21:40 UTCEPSS rescore
  7. 2026-08-27 14:24 UTCEPSS rescore
  8. 2026-08-26 14:45 UTCEPSS rescore
  9. 2026-08-25 13:48 UTCEPSS rescore
  10. 2026-08-24 14:16 UTCEPSS rescore
  11. 2026-08-23 00:18 UTCEPSS rescore
  12. 2026-08-21 23:48 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:46 UTCEPSS rescore
  17. 2026-08-16 14:55 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 23:31 UTCVendor advisory
  21. 2026-08-14 23:31 UTCGHSA enrichment
  22. 2026-08-14 11:59 UTCEG score recompute
  23. 2026-08-14 11:59 UTCVendor advisory
  24. 2026-08-14 11:59 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-08-13 04:05 UTCEG score recompute
  2. 2026-08-13 04:05 UTCVendor advisory
  3. 2026-08-13 04:05 UTCGHSA enrichment
  4. 2026-08-12 13:50 UTCEPSS rescore
  5. 2026-08-11 13:42 UTCEPSS rescore
  6. 2026-08-10 23:59 UTCEPSS rescore
  7. 2026-08-10 10:16 UTCVendor advisory
  8. 2026-08-10 10:16 UTCGHSA enrichment
  9. 2026-08-09 16:37 UTCEG score recompute
  10. 2026-08-09 16:37 UTCVendor advisory
  11. 2026-08-09 16:37 UTCGHSA enrichment
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-08 16:36 UTCEPSS rescore
  14. 2026-08-07 23:16 UTCEG score recompute
  15. 2026-08-07 23:16 UTCVendor advisory
  16. 2026-08-07 23:16 UTCGHSA enrichment
  17. 2026-08-07 16:27 UTCEPSS rescore
  18. 2026-08-06 13:46 UTCEPSS rescore
  19. 2026-08-06 04:46 UTCEG score recompute
  20. 2026-08-06 04:46 UTCVendor advisory
  21. 2026-08-06 04:46 UTCGHSA enrichment
  22. 2026-08-05 19:17 UTCEPSS rescore
  23. 2026-08-04 10:37 UTCEPSS rescore
  24. 2026-08-02 21:55 UTCEG score recompute
  25. 2026-08-02 21:55 UTCVendor advisory
  26. 2026-08-02 21:55 UTCGHSA enrichment
  27. 2026-08-02 02:26 UTCEPSS rescore
  28. 2026-08-01 04:15 UTCEPSS rescore
  29. 2026-07-31 05:42 UTCOSV refresh
  30. 2026-07-30 16:27 UTCEPSS rescore
  31. 2026-07-30 01:30 UTCEPSS rescore
  32. 2026-07-27 14:13 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 14:54 UTCEPSS rescore
  35. 2026-07-25 14:17 UTCEPSS rescore
  36. 2026-07-25 14:17 UTCEPSS rescore
  37. 2026-07-24 14:17 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 03:02 UTCEG score recompute
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 17:08 UTCEPSS rescore
  44. 2026-07-19 14:30 UTCEPSS rescore
  45. 2026-07-19 14:30 UTCEPSS rescore
  46. 2026-07-19 02:28 UTCEPSS rescore
  47. 2026-07-19 02:28 UTCEPSS rescore
  48. 2026-07-18 10:04 UTCEPSS rescore
  49. 2026-07-18 10:04 UTCEPSS rescore
  50. 2026-07-16 17:02 UTCEPSS rescore
  51. 2026-07-16 17:02 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 16:57 UTCEPSS rescore
  54. 2026-07-15 02:00 UTCEPSS rescore
  55. 2026-07-15 01:59 UTCEPSS rescore
  56. 2026-07-13 13:37 UTCOSV refresh
  57. 2026-07-13 06:12 UTCEPSS rescore
  58. 2026-07-12 05:46 UTCEPSS rescore
  59. 2026-07-12 05:46 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 19:10 UTCEPSS rescore
  63. 2026-07-08 15:15 UTCEPSS rescore
  64. 2026-07-07 13:46 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-05 02:30 UTCEPSS rescore
  68. 2026-07-05 02:30 UTCEPSS rescore
  69. 2026-07-04 06:31 UTCEPSS rescore
  70. 2026-07-04 06:31 UTCEPSS rescore
  71. 2026-07-01 15:06 UTCEPSS rescore
  72. 2026-06-30 23:22 UTCEPSS rescore
  73. 2026-06-30 23:22 UTCEPSS rescore
  74. 2026-06-29 14:06 UTCEPSS rescore
  75. 2026-06-29 14:06 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-68119?
CVE-2025-68119 is a high vulnerability published on January 28, 2026. Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This…
When was CVE-2025-68119 disclosed?
CVE-2025-68119 was first published in the National Vulnerability Database on January 28, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68119 actively exploited?
CVE-2025-68119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.2% of all scored CVEs.
What is the CVSS score of CVE-2025-68119?
CVE-2025-68119 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2025-68119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68119

Explore →

Is Your Infrastructure Affected by CVE-2025-68119?

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

Start Free Scan →Browse All CVEs