CVE-2026-44454

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 2.6% (85th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-42087 (ENISA EUVD) · GHSA-m3cr-vc2j-pm27 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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: 2.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7 and 2.30.2, the dotfiles registry module passed unsanitized user input to shell commands, allowing arbitrary code execution inside a provisioned workspace. Any user who supplied a crafted dotfiles_uri value (for example, one containing shell command substitution such as $(...)) could achieve command execution in their own workspace. The Create Workspace page's mode=auto deep links amplified this into a one-click attack: an attacker could craft a URL that prefilled param.dotfiles_uri and silently provisioned a workspace with the attacker-controlled value, with no explicit user confirmation. In versions 2.29.7 and 2.30.2, input validation was added to the dotfiles module to reject URIs and usernames containing special characters, and the unsafe eval/sh -c usage was removed. This eliminated the command injection at its source.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
41
EG Risk 41/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.6% × 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
2.6%
EPSS %ILE
85th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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.

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

July 2, 2026

Last Modified

July 8, 2026

Advisory Details (7)

Auto-updated Jul 7, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub pull request Patch Available

fix: add validation to inputs in dot-files module

Patch available: coder/registry release/coder/jetbrains/v1.4.0 (PR #703 merged 2026-02-09)

https://github.com/coder/registry/pull/703
GitHub commit Patch Available

commit 8e68c96633f6 (coder/registry)

Patch available: coder/registry release/coder/jetbrains/v1.4.0 (contains commit 8e68c96633f6)

https://github.com/coder/registry/commit/8e68c96633f65a1babd76a93b6923e3deead4a82
GitHub advisoryMentions a patch (unverified)

Command injection via dotfiles URI parameter combined with workspace auto-creation · Advisory · coder/coder · GitHub

https://github.com/coder/coder/security/advisories/GHSA-m3cr-vc2j-pm27
GitHub release Patch Available

v2.30.2

Patch available: coder/coder v2.30.2

https://github.com/coder/coder/releases/tag/v2.30.2
GitHub release Patch Available

v2.29.7

Patch available: coder/coder v2.29.7

https://github.com/coder/coder/releases/tag/v2.29.7
GitHub pull request

feat(site)!: add consent prompt for auto-creation with prefilled parameters

Fix merged in coder/coder PR #22011 on 2026-02-12 — awaiting tagged release

https://github.com/coder/coder/pull/22011
GitHub commit

commit 60e3ab7632f4 (coder/coder)

Fix landed in coder/coder commit 60e3ab7632f4 — awaiting tagged release

https://github.com/coder/coder/commit/60e3ab7632f42415d283b9fd5622ee53a4639ceb

Vendor Advisories for CVE-2026-44454(1)

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

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/coder/coder—
  • every version through 0.27.3: no fix on record
  • every version on: no fix on record
—
github.com/coder/coder/v2—
  • every version up to 2.29.7: fixed in 2.29.7
  • 2.30.0 up to 2.30.2: fixed in 2.30.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× 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 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 100 of 149 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. None are among the latest 100 rows. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-44454?
CVE-2026-44454 is a high-severity vulnerability; its CVE record was published on July 2, 2026. Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7 and 2.30.2, the dotfiles registry module passed unsanitized user input to shell commands, allowing arbitrary code execution inside a provisioned workspace. Any user who supplied a crafted…
When was the CVE record for CVE-2026-44454 published?
The CVE record for CVE-2026-44454 was published on July 2, 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 July 8, 2026; the record at its source may have been updated since.
Is CVE-2026-44454 actively exploited?
CVE-2026-44454 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44454?
CVE-2026-44454 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44454?
A fix for CVE-2026-44454 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44454 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-44454

Explore →

Is Your Infrastructure Affected by CVE-2026-44454?

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