{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41896 exists.","fix":"No fix has been published for CVE-2026-41896 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41896 is a high-severity authentication bypass vulnerability in coollabsio coolify, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41896 and fix it if it is affected.\n\nWhat it is: CVE-2026-41896 is a high-severity authentication bypass vulnerability in coollabsio coolify, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41896 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-41896/ (Markdown: https://insights.sbomify.com/CVE-2026-41896/index.md)","id":"CVE-2026-41896","markdown":"https://insights.sbomify.com/CVE-2026-41896/index.md","name":"CVE-2026-41896","record":{"aliases":["GHSA-w8wm-r924-f65v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Coolify self-hosted platform","requires_auth":"none","summary":"Unauthenticated attackers can forge webhook signatures using a null secret to trigger unauthorized deployments in Coolify.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, the HMAC key is the application's manual_webhook_secret_github field, which is used by Coolify's webhook endpoints to validate incoming requests, is nullable with no default — meaning newly created applications have a null webhook secret. PHP's hash_hmac() function silently coerces a null key to an empty string ''. So when the secret is null, the server computes hash_hmac('sha256', $payload, '') — a deterministic value that any attacker can calculate independently. By sending X-Hub-Signature-256: sha256=\u003chash_hmac('sha256', payload, '')\u003e, an unauthenticated attacker can forge a valid signature and trigger deployments. This vulnerability is fixed in 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: Unauthenticated Deployment Trigger via Webhook HMAC Bypass with Null Secret","id":"CVE-2026-41896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MantisBT: Reflected XSS in Rendering Dynamic Custom Textarea Field","id":"CVE-2026-41897"},"packages":[],"prev":{"headline":"changedetection.io: XXE vulnerability in the changedetection.io project","id":"CVE-2026-41895"},"products":["coolify"],"published":"2026-06-29","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-30","vendors":["coollabsio"]},"summary":"Unauthenticated attackers can forge webhook signatures using a null secret to trigger unauthorized deployments in Coolify.","url":"https://insights.sbomify.com/CVE-2026-41896/"}