{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42172 exists.","fix":"No fix has been published for CVE-2026-42172 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42172 is a low-severity vulnerability in coollabsio coolify, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42172 and fix it if it is affected.\n\nWhat it is: CVE-2026-42172 is a low-severity vulnerability in coollabsio coolify, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42172 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-2026-42172/ (Markdown: https://insights.sbomify.com/CVE-2026-42172/index.md)","id":"CVE-2026-42172","markdown":"https://insights.sbomify.com/CVE-2026-42172/index.md","name":"CVE-2026-42172","record":{"aliases":["GHSA-c83f-5ph7-x8xv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Coolify self-hosted platform","requires_auth":"low_privilege","summary":"Attackers with leaked API tokens retain permanent access to Coolify instances because tokens lack expiration, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, Sanctum API tokens did not expire, allowing a leaked token to retain access indefinitely until manually revoked. This issue is fixed in version 4.0.0-beta.474.","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: Sanctum API Tokens Have No Expiration — Leaked Tokens Grant Permanent Access","id":"CVE-2026-42172","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Kirby: User avatar creation, replacement and deletion are not gated by user update permissions","id":"CVE-2026-42174"},"packages":[],"prev":{"headline":"Privilege escalation in Nullsoft Scriptable Install System","id":"CVE-2026-42171"},"products":["coolify"],"published":"2026-07-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-07-07","vendors":["coollabsio"]},"summary":"Attackers with leaked API tokens retain permanent access to Coolify instances because tokens lack expiration, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2026-42172/"}