{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34167 exists.","fix":"No fix has been published for CVE-2026-34167 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34167 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 6 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-34167 and fix it if it is affected.\n\nWhat it is: CVE-2026-34167 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 6 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-34167 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-34167/ (Markdown: https://insights.sbomify.com/CVE-2026-34167/index.md)","id":"CVE-2026-34167","markdown":"https://insights.sbomify.com/CVE-2026-34167/index.md","name":"CVE-2026-34167","record":{"aliases":["GHSA-962v-gxmw-56hc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Coolify self-hosting platform","requires_auth":"low_privilege","summary":"Authenticated users can read cross-tenant activity logs and sensitive command outputs due to missing authorization checks in the ActivityMonitor component.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, the ActivityMonitor Livewire component exposes a public $activityId property without Livewire's #[Locked] attribute. It loads activities via Activity::find($this-\u003eactivityId) with no authorization or team scoping. Activity IDs are auto-incrementing integers. Any authenticated user can enumerate activity records across all teams and read the full command output from remote SSH processes, which may include secrets, configuration files, and infrastructure details. This issue is fixed in version 4.0.0-beta.471.","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: Cross-tenant activity log disclosure via unlocked Livewire property in ActivityMonitor","id":"CVE-2026-34167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Coolify: Command injection via unsanitized persistent storage name in docker volume commands","id":"CVE-2026-34168"},"packages":[],"prev":{"headline":"LiquidJS has a Memory Limit Bypass via Quadratic Amplification in `replace` Filter","id":"CVE-2026-34166"},"products":["coolify"],"published":"2026-07-06","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-08","vendors":["coollabsio"]},"summary":"Authenticated users can read cross-tenant activity logs and sensitive command outputs due to missing authorization checks in the ActivityMonitor component.","url":"https://insights.sbomify.com/CVE-2026-34167/"}