{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22607 exists.","fix":"No fix has been published for CVE-2025-22607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22607 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22607 and fix it if it is affected.\n\nWhat it is: CVE-2025-22607 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22607 exists.\n\nAffected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-22607/ (Markdown: https://insights.sbomify.com/CVE-2025-22607/index.md)","id":"CVE-2025-22607","markdown":"https://insights.sbomify.com/CVE-2025-22607/index.md","name":"CVE-2025-22607","record":{"aliases":["GHSA-8w24-gfgq-jg72"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Coolify self-hosting platform","requires_auth":"low_privilege","summary":"Authenticated users can access sensitive OAuth secrets for any GitHub or GitLab configuration by guessing UUIDs, requiring an upgrade to Coolify.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"coolify","vendor":"coollabs"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Coolify Vulnerable to GitHub / GitLab OAuth Secrets Leak","id":"CVE-2025-22607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Coolify Vulnerable to Revocation of Arbitrary Team Invitations (DOS)","id":"CVE-2025-22608"},"packages":[],"prev":{"headline":"Coolify Command Injection Vulnerability in Project Name","id":"CVE-2025-22606"},"products":["coolify"],"published":"2025-01-24","related":[{"cvss_score":10,"headline":"Coolify has Git Repository RCE","id":"CVE-2025-59157","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":10,"headline":"Coolify members can see private key of root user","id":"CVE-2025-64420","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":10,"headline":"Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup","id":"CVE-2025-66209","kev_date_added":null,"published":"2025-12-23"},{"cvss_score":10,"headline":"Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE)","id":"CVE-2025-22609","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":10,"headline":"Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE)","id":"CVE-2025-22611","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":10,"headline":"Coolify Vulnerable to Private Key Enumeration on Onboarding resulting in Remote Command Execution (RCE)","id":"CVE-2025-22612","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":9.7,"headline":"Coolify vulnerable to command injection via docker-compose.yaml parameters","id":"CVE-2025-64419","kev_date_added":null,"published":"2026-01-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-24","vendors":["coollabsio"]},"summary":"Authenticated users can access sensitive OAuth secrets for any GitHub or GitLab configuration by guessing UUIDs, requiring an upgrade to Coolify.","url":"https://insights.sbomify.com/CVE-2025-22607/"}