{"answers":{"affected":"2 open source packages ship an affected version, including kimai/kimai.","exploited":"There is no known exploitation of CVE-2026-52821 in the wild and no public exploit code.","fix":"Upgrade kimai/kimai to 2.57.0 or later.","what":"CVE-2026-52821 is a medium-severity missing authorization vulnerability in kimai, published on 15 Sep 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-52821 and fix it if it is affected.\n\nWhat it is: CVE-2026-52821 is a medium-severity missing authorization vulnerability in kimai, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-52821 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kimai/kimai (Packagist): affected all versions; fixed in 2.57.0\n- kimai/kimai (Packagist): affected all versions; fixed in 2.57.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-52821/ (Markdown: https://insights.sbomify.com/CVE-2026-52821/index.md)","id":"CVE-2026-52821","markdown":"https://insights.sbomify.com/CVE-2026-52821/index.md","name":"CVE-2026-52821","record":{"aliases":["GHSA-3q6q-26vg-v97x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kimai time tracking","requires_auth":"low_privilege","summary":"Attackers with basic creation rights can create activities or projects under unauthorized parents, corrupting billing and reporting data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Kimai is an open-source time tracking application. Prior to 2.57.0, GET or POST requests to /en/admin/activity/create/{project} and /en/admin/project/create/{customer} require only the generic create_activity or create_project capability and do not verify edit access to the supplied Project or Customer object. A user who knows a valid project.id or customer identifier can use the preset-parent creation logic in src/Controller/ActivityController.php or src/Controller/ProjectController.php to persist a new child business object under an unauthorized parent, polluting project or customer configuration and influencing later time-entry, rate, reporting, and billing behavior. This issue is fixed in version 2.57.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Kimai: Improper Authorization Through Activity Creation with Preset Project Allows Creation Under Unauthorized Projects","id":"CVE-2026-52821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation","id":"CVE-2026-52822"},"packages":[{"ecosystem":"Packagist","fixed":["2.57.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":null,"source":"GHSA-3q6q-26vg-v97x"},{"ecosystem":"Packagist","fixed":["2.57.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":"pkg:composer/kimai/kimai","source":"GHSA-3q6q-26vg-v97x"}],"prev":{"headline":"Kimai: Timesheet PATCH/POST allows assigning to project outside user's team via query_builder OR-bypass","id":"CVE-2026-52820"},"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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["kimai"]},"summary":"Attackers with basic creation rights can create activities or projects under unauthorized parents, corrupting billing and reporting data.","url":"https://insights.sbomify.com/CVE-2026-52821/"}