{"answers":{"affected":"2 open source packages ship an affected version, including kimai/kimai.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52824 exists.","fix":"Upgrade kimai/kimai to 2.58.0 or later.","what":"CVE-2026-52824 is a critical vulnerability in kimai, published on 15 Sep 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-52824 and fix it if it is affected.\n\nWhat it is: CVE-2026-52824 is a critical vulnerability in kimai, published on 15 Sep 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-52824 exists.\n\nAffected packages and fixed versions:\n- kimai/kimai (Packagist): affected all versions; fixed in 2.58.0\n- kimai/kimai (Packagist): affected all versions; fixed in 2.58.0\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-52824/ (Markdown: https://insights.sbomify.com/CVE-2026-52824/index.md)","id":"CVE-2026-52824","markdown":"https://insights.sbomify.com/CVE-2026-52824/index.md","name":"CVE-2026-52824","record":{"aliases":["GHSA-jr9p-4h4j-6c58"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Kimai time tracking","requires_auth":"none","summary":"An unauthenticated attacker can forge authentication cookies to take over accounts in Kimai deployments using the default Docker image secret.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"Kimai is an open-source time tracking application. Prior to 2.58.0, the official Docker image sets APP_SECRET to the public value change_this_to_something_unique in Dockerfile, and .docker/entrypoint.sh neither replaces nor rejects that value before Symfony uses it as kernel.secret. An unauthenticated attacker who reaches a deployment that did not override APP_SECRET, knows a username, correctly guesses the account ID associated with that username, and targets an account without active two-factor authentication can forge HMAC-protected authentication artifacts, including KIMAI_REMEMBER cookies and login links, to access the account without its password. The updated entrypoint generates and persists a random secret when no safe operator-provided value exists. This issue is fixed in version 2.58.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":"2026-08-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-08-04T03:15:37Z","kind":"github_poc","ref":"https://github.com/AzureADTrent/CVE-2026-52824","stars":0,"title":"Technical analysis and PoC of CVE-2026-52824: default APP_SECRET in the Kimai Docker image enabling unauthenticated login link forgery. Affects \u003c= 2.57.0, fixed in 2.58.0."},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-52824.yaml","stars":null,"title":"Kimai \u003c= 2.57.0 - Default APP_SECRET Authentication Bypass"}],"tier":"weaponised"},"has_fix":true,"headline":"Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover","id":"CVE-2026-52824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Kimai has Improper Authorization in Team Member and Team Activity Assignment APIs Which Allows Expansion of Team Scope Beyond Authorized Visibility","id":"CVE-2026-52825"},"packages":[{"ecosystem":"Packagist","fixed":["2.58.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":null,"source":"GHSA-jr9p-4h4j-6c58"},{"ecosystem":"Packagist","fixed":["2.58.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":"pkg:composer/kimai/kimai","source":"GHSA-jr9p-4h4j-6c58"}],"prev":{"headline":"Kimai: Login CSRF in Kimai Timesheet Stop and Restart API Endpoints Allows Unauthorized State Changes","id":"CVE-2026-52823"},"products":["kimai"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["kimai"]},"summary":"An unauthenticated attacker can forge authentication cookies to take over accounts in Kimai deployments using the default Docker image secret.","url":"https://insights.sbomify.com/CVE-2026-52824/"}