{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-22610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-22610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22610 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 24 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22610 and fix it if it is affected.\n\nWhat it is: CVE-2025-22610 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 24 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-22610 in the wild and no public exploit code.\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-22610/ (Markdown: https://insights.sbomify.com/CVE-2025-22610/index.md)","id":"CVE-2025-22610","markdown":"https://insights.sbomify.com/CVE-2025-22610/index.md","name":"CVE-2025-22610","record":{"aliases":["GHSA-496v-9q38-2x6c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Coolify self-hosting platform","requires_auth":"low_privilege","summary":"Authenticated users can read and modify global OAuth secrets due to missing authorization checks in 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":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/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"}],"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 global coolify instance OAuth configuration. This exposes the \"client id\" and \"client secret\" for every custom OAuth provider. The attacker can also modify the global OAuth configuration. Version 4.0.0-beta.361 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Coolify Vulnerable to OAuth Secrets Leak","id":"CVE-2025-22610","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 Privilege Escalation resulting in Remote Command Execution (RCE)","id":"CVE-2025-22611"},"packages":[],"prev":{"headline":"Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE)","id":"CVE-2025-22609"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-24","vendors":["coollabsio"]},"summary":"Authenticated users can read and modify global OAuth secrets due to missing authorization checks in Coolify.","url":"https://insights.sbomify.com/CVE-2025-22610/"}