CVE-2026-31886

CRITICALNVD 7.69.1
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-13. NVD baseline CVSS 7.6; sources differ by 1.5.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-12089 (ENISA EUVD) · GHSA-m4q3-457p-hh2x (GitHub Security Advisories) · GO-2026-4693 (OSV.dev)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.5%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Dagu is a workflow engine with a built-in Web user interface. Prior to 2.2.4, the dagRunId request field accepted by the inline DAG execution endpoints is passed directly into filepath.Join to construct a temporary directory path without any format validation. Go's filepath.Join resolves .. segments lexically, so a caller can supply a value such as ".." to redirect the computed directory outside the intended /tmp// path. A deferred cleanup function that calls os.RemoveAll on that directory then runs unconditionally when the HTTP handler returns, deleting whatever directory the traversal resolved to. With dagRunId set to "..", the resolved directory is the system temporary directory (/tmp on Linux). On non-root deployments, os.RemoveAll("/tmp") removes all files in /tmp owned by the dagu process user, disrupting every concurrent dagu run that has live temp files. On root or Docker deployments, the call removes the entire contents of /tmp, causing a system-wide denial of service. This vulnerability is fixed in 2.2.4.

CVSS v3
7.6
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% 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: 60 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).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (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.

The score's inputs: 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

March 13, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Path Traversal via `dagRunId` in Inline DAG Execution · Advisory · dagucloud/dagu · GitHub

https://github.com/dagu-org/dagu/security/advisories/GHSA-m4q3-457p-hh2x
GitHub commit

commit 12c2e5395bd9 (dagu-org/dagu)

Fix landed in dagu-org/dagu commit 12c2e5395bd9 — awaiting tagged release

https://github.com/dagu-org/dagu/commit/12c2e5395bd9331d49ca103593edfd0db39c4f38

Vendor Advisories for CVE-2026-31886(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/dagu-org/dagu—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/dagu-org/dagu—
  • every version through 2.2.4: no fix on record
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 61× 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 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). "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 218 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 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-31886?
CVE-2026-31886 is a critical-severity vulnerability; its CVE record was published on March 13, 2026. Dagu is a workflow engine with a built-in Web user interface. Prior to 2.2.4, the dagRunId request field accepted by the inline DAG execution endpoints is passed directly into filepath.Join to construct a temporary directory path without any format validation. Go's filepath.Join resolves ..…
When was the CVE record for CVE-2026-31886 published?
The CVE record for CVE-2026-31886 was published on March 13, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-31886 actively exploited?
CVE-2026-31886 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31886?
CVE-2026-31886 has a CVSS v3 base score of 7.6 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.1 (CRITICAL).
How do I remediate CVE-2026-31886?
The CVE record for CVE-2026-31886 names the fix: "This vulnerability is fixed in 2.2.4." The vendor advisories EchelonGraph has for CVE-2026-31886 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-31886

Explore →

Is Your Infrastructure Affected by CVE-2026-31886?

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