{"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-80202 exists.","fix":"Upgrade kimai/kimai to 2.56.0 or later.","what":"CVE-2026-80202 is a critical missing authorization vulnerability in kimai, published on 25 Aug 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-80202 and fix it if it is affected.\n\nWhat it is: CVE-2026-80202 is a critical missing authorization vulnerability in kimai, published on 25 Aug 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-80202 exists.\n\nAffected packages and fixed versions:\n- kimai/kimai (Packagist): affected all versions; fixed in 2.56.0\n- kimai/kimai (Packagist): affected all versions; fixed in 2.56.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-80202/ (Markdown: https://insights.sbomify.com/CVE-2026-80202/index.md)","id":"CVE-2026-80202","markdown":"https://insights.sbomify.com/CVE-2026-80202/index.md","name":"CVE-2026-80202","record":{"aliases":["GHSA-9g2q-w3w2-vf7q","GHSA-fx95-9ppf-x8wm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kimai time tracking","requires_auth":"none","summary":"Authenticated team leads can read, modify, and delete any user's timesheets system-wide due to missing team membership checks in the API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Kimai before 2.56.0 does not enforce team-membership checks in TimesheetVoter::voteOnAttribute(), which maps permissions only to own_timesheet or other_timesheet. As a result, any authenticated user with ROLE_TEAMLEAD (or a role holding edit_other_timesheet/delete_other_timesheet) can read, modify, and permanently delete timesheets belonging to any user system-wide via the API, regardless of team membership. Timesheet IDs are sequential integers and trivially enumerable. ROLE_USER accounts are correctly restricted. (Note: the maintainers characterize this behavior as matching the documented permission model.)","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Kimai before 2.56.0 Authorization Bypass via TimesheetVoter","id":"CVE-2026-80202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Grav before 1.0.18 Authentication Bypass via Scoped API Key","id":"CVE-2026-80203"},"packages":[{"ecosystem":"Packagist","fixed":["2.56.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":null,"source":"GHSA-9g2q-w3w2-vf7q"},{"ecosystem":"Packagist","fixed":["2.56.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":"pkg:composer/kimai/kimai","source":"GHSA-9g2q-w3w2-vf7q"}],"prev":{"headline":"Kimai before 2.53.0 API Token Leakage via Invoice Template","id":"CVE-2026-80201"},"products":["kimai"],"published":"2026-08-25","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["kimai"]},"summary":"Authenticated team leads can read, modify, and delete any user's timesheets system-wide due to missing team membership checks in the API.","url":"https://insights.sbomify.com/CVE-2026-80202/"}