CVE-2026-27883

MEDIUMPre-NVD 5.05.0
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.0Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.464, the GET /api/v1/deployments/{uuid} endpoint allows any authenticated user to access deployment details belonging to any team, bypassing team-based authorization. The $teamId is extracted from the authentication token but never used to scope the database query. This vulnerability is fixed in 4.0.0-beta.464.

CVSS v3
5.0
EG Score
5.0MEDIUMmedium confidence
EG Risk
23
EG Risk 23/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity50% × 45%
The EG Score, 5.0 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.4%
EPSS %ILE
27th
KEV
Not listed

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 none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (1)

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

IDOR in Deployment API - Cross-Team Deployment Information Disclosure · Advisory · coollabsio/coolify · GitHub

https://github.com/coollabsio/coolify/security/advisories/GHSA-f6h4-qx26-76jv

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27883?
CVE-2026-27883 is a medium-severity vulnerability; its CVE record was published on June 30, 2026. Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.464, the GET /api/v1/deployments/{uuid} endpoint allows any authenticated user to access deployment details belonging to any team, bypassing team-based authorization. The $teamId…
When was the CVE record for CVE-2026-27883 published?
The CVE record for CVE-2026-27883 was published on June 30, 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 1, 2026; the record at its source may have been updated since.
Is CVE-2026-27883 actively exploited?
CVE-2026-27883 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27883?
CVE-2026-27883 has a CVSS base score of 5.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-27883?
The CVE record for CVE-2026-27883 names the fix: "This vulnerability is fixed in 4.0.0-beta.464."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-27883?

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

Book a Demo →Browse All CVEs