CVE-2025-22605

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (43rd 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
Elevated

Also known asEUVD-2025-2879 (ENISA EUVD)Source: ENISA EUVD

7.8EG
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.5%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Starting in version 4.0.0-beta.18 and prior to 4.0.0-beta.253, a vulnerability in the execution of commands on remote servers allows an authenticated user to execute arbitrary code on the local Coolify container, gaining access to data and private keys or tokens of other users/teams. The ability to inject malicious commands into the Coolify container gives authenticated attackers the ability to fully retrieve and control the data and availability of the software. Centrally hosted Coolify instances (open registration and/or multiple teams with potentially untrustworthy users) are especially at risk, as sensitive data of all users and connected servers can be leaked by any user. Additionally, attackers are able to modify the running software, potentially deploying malicious images to remote nodes or generally changing its behavior. Version 4.0.0-beta.253 patches this issue.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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.5%
EPSS %ILE
43rd
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.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
0.5% within 30 daysSource: FIRST EPSS. 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

January 24, 2025

Last Modified

September 19, 2025

Advisory Details (5)

Auto-updated Oct 11, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

OS Command Injection Vulnerability in SSH Command Generation · Advisory · coollabsio/coolify · GitHub

https://github.com/coollabsio/coolify/security/advisories/GHSA-9wqm-fg79-4748
GitHub pull request Patch Available

v4.0.0-beta.186

Patch available: coollabsio/coolify v4.3.2 (PR #1625 merged 2024-01-11)

https://github.com/coollabsio/coolify/pull/1625
GitHub pull request Patch Available

Add support for command execution in containers.

Patch available: coollabsio/coolify v4.3.2 (PR #1524 merged 2023-12-07)

https://github.com/coollabsio/coolify/pull/1524
GitHub commit Patch Available

commit 353245bb7de9 (coollabsio/coolify)

Patch available: coollabsio/coolify v4.3.2 (contains commit 353245bb7de9)

https://github.com/coollabsio/coolify/commit/353245bb7de9680f238bae30443af1696bc977b0
Web page

coolify/bootstrap/helpers/remoteProcess.php at 40a239ddda3fc919f57a052d7b52b8e1a6696b81 · coollabsio/coolify · GitHub

https://github.com/coollabsio/coolify/blob/40a239ddda3fc919f57a052d7b52b8e1a6696b81/bootstrap/helpers/remoteProcess.php#L70

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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 96 of 195 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-22605?
CVE-2025-22605 is a high-severity vulnerability; its CVE record was published on January 24, 2025. Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Starting in version 4.0.0-beta.18 and prior to 4.0.0-beta.253, a vulnerability in the execution of commands on remote servers allows an authenticated user to execute arbitrary code on the local…
When was the CVE record for CVE-2025-22605 published?
The CVE record for CVE-2025-22605 was published on January 24, 2025. 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 September 19, 2025; the record at its source may have been updated since.
Is CVE-2025-22605 actively exploited?
CVE-2025-22605 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-22605?
CVE-2025-22605 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-22605?
A fix for CVE-2025-22605 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-22605

Explore →

Is Your Infrastructure Affected by CVE-2025-22605?

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