CVE-2026-64672

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th 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

Also known asEUVD-2026-116370 (ENISA EUVD) · GHSA-wv6g-x823-wx9m (GitHub Security Advisories) · GO-2026-6768 (OSV.dev)Source: ENISA EUVD

4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu or Terraform to scale. Prior to 1.1.1, the terragrunt catalog command derives a predictable per-repository catalog clone root under the shared system temporary directory and follows a symlink already placed at that path. A local attacker who can write to the temporary directory and predict the cataloged repository can redirect cleanup and cloning outside the intended root, causing an existing repository-named directory to be deleted and replaced in the victim's security context. The attack requires the victim to run terragrunt catalog on a shared host while the symlink is present, and it is not remotely exploitable. This issue is fixed in version 1.1.1.

CVSS
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
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 (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-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-12). 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: 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 or medium mission impact; Track* at high (mission-essential systems).

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

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

October 15, 2026

Last Modified

November 12, 2026

Advisory Details (4)

Auto-updated Nov 7, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

v1.1.1

Patch available: gruntwork-io/terragrunt v1.1.1

https://github.com/gruntwork-io/terragrunt/releases/tag/v1.1.1
GitHub commit

commit 668891c5a2ad (gruntwork-io/terragrunt)

Fix landed in gruntwork-io/terragrunt commit 668891c5a2ad — awaiting tagged release

https://github.com/gruntwork-io/terragrunt/commit/668891c5a2ad2996f134bb8b00098754674ea94a
GitHub pull request

fix(catalog): harden temporary clone paths

Fix merged in gruntwork-io/terragrunt PR #6438 on 2026-07-07 — awaiting tagged release

https://github.com/gruntwork-io/terragrunt/pull/6438
GitHub advisoryMentions a patch (unverified)

Terragrunt catalog predictable temp symlink clobber · Advisory · gruntwork-io/terragrunt · GitHub

https://github.com/gruntwork-io/terragrunt/security/advisories/GHSA-wv6g-x823-wx9m

Vendor Advisories for CVE-2026-64672(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/gruntwork-io/terragrunt @ 1.1.1 (fixes < 1.1.1)—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/gruntwork-io/terragrunt—
  • every version up to 1.1.1: fixed in 1.1.1
—

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-11-12 20:08 UTCEchelonGraph re-scored
  2. 2026-11-12 20:08 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-11-11 07:54 UTCEchelonGraph re-scored
  6. 2026-11-11 07:54 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-11-07 04:28 UTCEchelonGraph re-scored
  12. 2026-11-07 04:28 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  13. 2026-11-07 03:36 UTCEchelonGraph re-scored
  14. 2026-11-07 03:36 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  15. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-11-03 22:12 UTCENISA EUVD ID recordedEUVD-2026-116370 · Source: ENISA EUVD
  19. 2026-11-03 21:29 UTCEchelonGraph re-scored
  20. 2026-11-03 21:29 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  21. 2026-11-03 20:48 UTCEchelonGraph re-scoredFirst assessed: 4.4 MEDIUM
  22. 2026-11-03 20:48 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  23. 2026-11-03 20:46 UTCMITRE cvelistV5CVSS → 4.4 · CVSS v4 → 4.4
  24. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-wv6g-x823-wx9m · GitHub severity MODERATE
  25. 2026-10-25 14:12 UTCEchelonGraph re-scored
Show 2 more
  1. 2026-10-18 03:22 UTCEchelonGraph re-scored
  2. 2026-10-15 18:28 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/gruntwork-io/terragrunt

Frequently asked(5)

What is CVE-2026-64672?
CVE-2026-64672 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu or Terraform to scale. Prior to 1.1.1, the terragrunt catalog command derives a predictable per-repository catalog clone root under the shared system temporary directory and follows a symlink already…
When was the CVE record for CVE-2026-64672 published?
The CVE record for CVE-2026-64672 was published on October 15, 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 November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-64672 actively exploited?
CVE-2026-64672 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-64672?
CVE-2026-64672 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64672?
A fix for CVE-2026-64672 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64672 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-64672

Explore →

Is Your Infrastructure Affected by CVE-2026-64672?

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

Book a Demo →Browse All CVEs