CVE-2025-34157

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2025-08-27. NVD baseline CVSS 9.0; sources differ by 0.0.

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

Also known asEUVD-2025-25910 (ENISA EUVD) · GHSA-6p37-qg9q-mprw (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (VulnCheck) states them: "The project maintainer has confirmed that this vulnerability was remediated in version 4.0.0.-beta.420.7 despite not being acknowledged in the release notes."

Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. An authenticated user with low privileges can create a project with a maliciously crafted name containing embedded JavaScript. When an administrator attempts to delete the project or its associated resource, the payload executes in the admin’s browser context. This results in full compromise of the Coolify instance, including theft of API tokens, session cookies, and access to WebSocket-based terminal sessions on managed servers.

CVSS v3
9.0
EG Score
9.0CRITICALmedium 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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
41st
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 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: 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

August 27, 2025

Last Modified

November 8, 2026

Advisory Details (3)

Auto-updated Jul 14, 2026
Patch available. Sources: github_release.
GitHub release Patch Available

v4.0.0.-beta.420.7

Patch available: coollabsio/coolify v4.0.0-beta.420.7

https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.420.7
Web page

GitHub - Eyodav/CVE-2025-34157: A stored XSS in the project delete flow allows execution of attacker-controlled JavaScript in an administrator’s browser when the admin attempts to delete a project created by a low-privileged user. This can lead to takeover of the Coolify instance (cookies, API tokens, WebSocket/terminal actions) · GitHub

https://github.com/Eyodav/CVE-2025-34157
Web page

Coolify

https://coolify.io/

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 63× 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 267 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 167 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-34157?
CVE-2025-34157 is a critical-severity vulnerability; its CVE record was published on August 27, 2025. Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. An authenticated user with low privileges can create a project with a maliciously crafted name containing embedded JavaScript. When an administrator attempts to…
When was the CVE record for CVE-2025-34157 published?
The CVE record for CVE-2025-34157 was published on August 27, 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 November 8, 2026; the record at its source may have been updated since.
Is CVE-2025-34157 actively exploited?
CVE-2025-34157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-34157?
CVE-2025-34157 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2025-34157?
A fix for CVE-2025-34157 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (VulnCheck) states them: "The project maintainer has confirmed that this vulnerability was remediated in version 4.0.0.-beta.420.7 despite not being acknowledged in the release notes."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-34157?

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