CVE-2026-129433

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-14. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-125911 (ENISA EUVD) · GHSA-gfc5-hfj7-fjwc (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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.4%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Dokploy before 0.31.1 contains an OS command injection vulnerability in getComposeContainerCommand() that allows authenticated organization members to execute shell commands via the serviceName parameter. Attackers can store serviceName values with shell metacharacters through backup.create or backup.update tRPC procedures, executing commands as root when scheduled backups run and taking over the host via the mounted Docker socket.

CVSS v3
9.9
EG Score
9.9CRITICALhigh confidence
EG Risk
46
EG Risk 46/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.4% × 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.4%
EPSS %ILE
84th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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

November 14, 2026

Last Modified

November 16, 2026

Advisory Details (7)

Auto-updated Nov 16, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
Web page

Dokploy before 0.31.1 OS Command Injection via Compose Backup serviceName | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

OS Command Injection via serviceName in Compose Backup · Advisory · Dokploy/dokploy · GitHub

https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm
GitHub release Patch Available

v0.31.1

Patch available: Dokploy/dokploy v0.31.1

https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
GitHub pull request Patch Available

fix(security): backup prefix/bucket/serviceName command injection (member → root)

Patch available: Dokploy/dokploy v0.31.1 (PR #5908 merged 2026-11-11)

https://github.com/Dokploy/dokploy/pull/5908
GitHub commit Patch Available

commit b24006e16e95 (Dokploy/dokploy)

Patch available: Dokploy/dokploy v0.31.1 (contains commit b24006e16e95)

https://github.com/Dokploy/dokploy/commit/b24006e16e95a10ce3daf739d06ac783e5c70ba0
Web page

dokploy/packages/server/src/utils/backups/utils.ts at v0.31.0 · Dokploy/dokploy · GitHub

https://github.com/Dokploy/dokploy/blob/v0.31.0/packages/server/src/utils/backups/utils.ts#L152
Web page

GitHub - Dokploy/dokploy: Open Source Alternative to Vercel, Netlify and Heroku. · GitHub

https://github.com/Dokploy/dokploy

Vendor Advisories for CVE-2026-129433(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-22 18:04 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  2. 2026-11-21 19:49 UTCEchelonGraph re-scored
  3. 2026-11-21 19:49 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-21 16:38 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  5. 2026-11-20 21:32 UTCEchelonGraph re-scored
  6. 2026-11-20 21:32 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-20 16:36 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  8. 2026-11-19 23:16 UTCEchelonGraph re-scored
  9. 2026-11-19 23:16 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-19 16:33 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  11. 2026-11-19 14:18 UTCEchelonGraph re-scored
  12. 2026-11-19 14:18 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-18 16:34 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  14. 2026-11-18 16:02 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  15. 2026-11-17 17:46 UTCEchelonGraph re-scored
  16. 2026-11-17 17:46 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-11-17 16:34 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  18. 2026-11-16 19:30 UTCEchelonGraph re-scored
  19. 2026-11-16 19:30 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  20. 2026-11-16 16:49 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  21. 2026-11-16 12:22 UTCEchelonGraph re-scored
  22. 2026-11-16 12:22 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  23. 2026-11-15 16:57 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  24. 2026-11-15 14:03 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-11-14 15:47 UTCEchelonGraph re-scored
Show 5 more
  1. 2026-11-14 15:47 UTCGHSA enrichmentGHSA-gfc5-hfj7-fjwc · GitHub severity CRITICAL · GitHub CVSS 9.9
  2. 2026-11-14 13:28 UTCEchelonGraph re-scored
  3. 2026-11-14 13:02 UTCENISA EUVD ID recordedEUVD-2026-125911 · Source: ENISA EUVD
  4. 2026-11-14 12:46 UTCEchelonGraph re-scoredFirst assessed: 9.9 CRITICAL
  5. 2026-11-14 12:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129433?
CVE-2026-129433 is a critical-severity vulnerability; its CVE record was published on November 14, 2026. Dokploy before 0.31.1 contains an OS command injection vulnerability in getComposeContainerCommand() that allows authenticated organization members to execute shell commands via the serviceName parameter. Attackers can store serviceName values with shell metacharacters through backup.create or…
When was CVE-2026-129433 made public?
CVE-2026-129433 was made public on November 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 14, 2026. EchelonGraph's copy of the record carries a last-modified date of November 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129433 actively exploited?
CVE-2026-129433 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129433?
CVE-2026-129433 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129433?
A fix for CVE-2026-129433 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129433 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-129433?

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