CVE-2026-72718

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.0 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
Elevated

Also known asEUVD-2026-55653 (ENISA EUVD)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 7.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

goose is general-purpose AI agent that runs on your machine. Prior to 1.44.0, the goose review command runs the system git executable to gather the diff for review without stripping attacker-controlled Git configuration. A malicious repository whose .git/config sets [core] fsmonitor = causes Git to execute that command on the host during the index refresh performed by git diff HEAD. The command runs before goose contacts a model and without a submitted prompt, model call, tool approval, or trust prompt. The context-gathering Git process is not sandboxed and is outside goose's tool-permission model. Arbitrary commands run with the privileges and environment of the user running goose, allowing file access or modification and exfiltration of environment secrets and provider API keys. The vulnerable Git invocations are built by git_command() in crates/goose-cli/src/commands/review/handler.rs and are used by touched_files() and collect_diff() for git diff --name-only HEAD and git diff HEAD. This issue is fixed in version 1.44.0.

CVSS
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
12th
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 (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

August 10, 2026

Last Modified

October 24, 2026

Advisory Details (3)

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

Arbitrary command execution in goose CLI via `goose review` via git core.fsmonitor · Advisory · aaif-goose/goose · GitHub

https://github.com/aaif-goose/goose/security/advisories/GHSA-r5pp-p5r8-466r
GitHub release Patch Available

v1.44.0

Patch available: aaif-goose/goose v1.44.0

https://github.com/aaif-goose/goose/releases/tag/v1.44.0
GitHub commit

commit f8b5b7ba1fe6 (aaif-goose/goose)

Fix landed in aaif-goose/goose commit f8b5b7ba1fe6 — awaiting tagged release

https://github.com/aaif-goose/goose/commit/f8b5b7ba1fe6d006ccf6942f6b85a1bae985a2de

Vendor Advisories for CVE-2026-72718(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatgoose-0:1.45.0-1.el10_22026-10-12redhat
redhatgoose-0:1.45.0-1.el9_82026-10-12redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 158 rows 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. None are among the latest 100 rows. The 58 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-72718?
CVE-2026-72718 is a high-severity vulnerability; its CVE record was published on August 10, 2026. goose is general-purpose AI agent that runs on your machine. Prior to 1.44.0, the goose review command runs the system git executable to gather the diff for review without stripping attacker-controlled Git configuration. A malicious repository whose .git/config sets [core] fsmonitor = <command>…
When was the CVE record for CVE-2026-72718 published?
The CVE record for CVE-2026-72718 was published on August 10, 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-72718 actively exploited?
CVE-2026-72718 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-72718?
CVE-2026-72718 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72718?
A fix for CVE-2026-72718 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72718 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72718

Explore →

Is Your Infrastructure Affected by CVE-2026-72718?

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