dbcve.org
CoolifyApplication · Coollabs

CVE-2025-22607

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.361, the missing authorization allows any authenticated user to fetch the details page for any GitHub / GitLab configuration on a Coolify instance by only knowing the UUID of the model. This exposes the "client id", "client secret" and "webhook secret." Version 4.0.0-beta.361 fixes this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Missing authorization check in Coolify allows any authenticated user to access GitHub/GitLab configuration details by knowing the UUID, exposing sensitive credentials (client ID, client secret, webhook secret). This is an Insecure Direct Object Reference (IDOR) vulnerability.

MitigationUpgrade to Coolify version 4.0.0-beta.361 or later which adds proper authorization checks to prevent unauthorized access to GitHub/GitLab configuration details.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CoolifyApplication
Affected:< 4.0.0= 4.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Coolify installation
    Locate the Coolify instance in your environment. This may be a Docker container, a VM, or a Kubernetes deployment. Check for running services on common ports or look for coolify-related processes.
    Affected if Coolify is installed and running in your environment
  2. Determine installed Coolify version
    Access the Coolify admin panel or API to find the current version. Typically found in Settings > About or via the web interface footer. If using Docker, check the container image tag.
    Affected if The installed version is less than 4.0.0 or exactly 4.0.0
  3. Verify GitHub/GitLab integrations are configured
    Check if any GitHub or GitLab integrations are configured in Coolify. Look for projects or resources linked to Git repositories in the Coolify dashboard.
    Affected if GitHub or GitLab integrations are configured and accessible to authenticated users
  4. Review API access logs for configuration endpoints
    Examine Coolify API access logs or audit trails for requests to endpoints that return GitHub/GitLab configuration data (such as settings or resource endpoints). Look for unauthorized access patterns by users accessing configurations outside their permissions.
    Affected if Users can access GitHub/GitLab configuration endpoints via API without proper authorization checks

You are affected if Coolify version is less than 4.0.0 or exactly 4.0.0 and GitHub/GitLab integrations are configured, as any authenticated user could potentially access sensitive credentials through the vulnerable endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade to Coolify version 4.0.0-beta.361 or later which adds proper authorization checks to prevent unauthorized access to GitHub/GitLab configuration details.

Recommended fix High confidence

4.0.0-beta.361 or later

  1. Backup your current Coolify instance and database before upgrading
  2. Upgrade Coolify to version 4.0.0-beta.361 or later
  3. Verify the upgrade was successful by logging into the Coolify dashboard
  4. After upgrade, rotate any GitHub/GitLab credentials that may have been exposed through this vulnerability
Caveat This is a beta version upgrade; review beta release notes for potential compatibility issues with your existing configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coolify Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22607 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data