{"items":[{"id":"NVI-00006782","kind":"vulnerability","title":"Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c6w6-57jj-62vh","CVE-2026-52822"],"plain_summary":"GitHub lists this reviewed advisory for kimai/kimai. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-7574e82aff17e759f4926aa02c21c490"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.58.0 for kimai/kimai. Confirm the publisher’s latest guidance.","source_ids":["sr-c2650922499cf62d4b50f813a7809811"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.465%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.40283. Missing scores are unknown.","source_id":"sr-7574e82aff17e759f4926aa02c21c490"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-60f38b99272042fb706901426c58ac1d","url":"https://github.com/advisories/GHSA-c6w6-57jj-62vh","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-c6w6-57jj-62vh","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:34:12.429Z"},{"id":"sr-c2650922499cf62d4b50f813a7809811","url":"https://github.com/advisories/GHSA-c6w6-57jj-62vh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c6w6-57jj-62vh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.696Z"},{"id":"sr-7574e82aff17e759f4926aa02c21c490","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-52822","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-60f38b99272042fb706901426c58ac1d"],"technology":"kimai/kimai","known_exclusions":[],"conditions_summary":"### Summary\n\nKimai 2.56.0 contains an authenticated authorization bypass in the timesheet `restart` and `duplicate` workflows. After a user loses access to a project, the user can still derive a new timesheet from one of their historical entries and create a new record under that now-unauthorized project and activity combination.\n\nThis is a permission revocation bypass with persistent write impact. The issue affects both `restart` and `duplicate`, which trust ownership of an old timesheet more than the user's current access to the underlying project, activity, and customer.\n\n### Details\n\nThe issue affects the following operations:\n\n- `PATCH /api/timesheets/{id}/restart`\n- `PATCH /api/timesheets/{id}/duplicate`\n\nThe root cause is that authorization gives too much weight to the fact that the original timesheet belongs to the current user. In `src/Voter/TimesheetVoter.php`, the `*_own_timesheet` branch is evaluated before team-based access checks.\n\nThe restart/duplicate capability check also verifies only object visibility, not whether the current user still has team-based access to the referenced objects. \n\nIn `src/API/TimesheetController.php`, the restart flow copies the historical ","public_affected_ranges":["<= 2.57.0"]},{"certainty":"source_listed","source_ids":["sr-c2650922499cf62d4b50f813a7809811"],"technology":"kimai/kimai","known_exclusions":[],"conditions_summary":"### Summary\n\nKimai 2.56.0 contains an authenticated authorization bypass in the timesheet `restart` and `duplicate` workflows. After a user loses access to a project, the user can still derive a new timesheet from one of their historical entries and create a new record under that now-unauthorized project and activity combination.\n\nThis is a permission revocation bypass with persistent write impact. The issue affects both `restart` and `duplicate`, which trust ownership of an old timesheet more than the user's current access to the underlying project, activity, and customer.\n\n### Details\n\nThe issue affects the following operations:\n\n- `PATCH /api/timesheets/{id}/restart`\n- `PATCH /api/timesheets/{id}/duplicate`\n\nThe root cause is that authorization gives too much weight to the fact that the original timesheet belongs to the current user. In `src/Voter/TimesheetVoter.php`, the `*_own_timesheet` branch is evaluated before team-based access checks.\n\nThe restart/duplicate capability check also verifies only object visibility, not whether the current user still has team-based access to the referenced objects. \n\nIn `src/API/TimesheetController.php`, the restart flow copies the historical ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.58.0"]}],"null_published_at":"2026-11-05T19:10:21.466Z","source_updated_at":"2026-07-14T00:04:27.000Z","source_disclosed_at":"2026-07-14T00:04:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:10.696Z"},{"id":"NVI-00006782","kind":"vulnerability","title":"Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c6w6-57jj-62vh","CVE-2026-52822"],"plain_summary":"OSV carries this publisher advisory for kimai/kimai. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.58.0 for kimai/kimai. Confirm the publisher’s latest guidance.","source_ids":["sr-c2650922499cf62d4b50f813a7809811"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-7574e82aff17e759f4926aa02c21c490"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.465%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.40283. Missing scores are unknown.","source_id":"sr-7574e82aff17e759f4926aa02c21c490"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c2650922499cf62d4b50f813a7809811","url":"https://github.com/advisories/GHSA-c6w6-57jj-62vh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c6w6-57jj-62vh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.696Z"},{"id":"sr-7574e82aff17e759f4926aa02c21c490","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-52822","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c2650922499cf62d4b50f813a7809811"],"technology":"kimai/kimai","known_exclusions":[],"conditions_summary":"### Summary\n\nKimai 2.56.0 contains an authenticated authorization bypass in the timesheet `restart` and `duplicate` workflows. After a user loses access to a project, the user can still derive a new timesheet from one of their historical entries and create a new record under that now-unauthorized project and activity combination.\n\nThis is a permission revocation bypass with persistent write impact. The issue affects both `restart` and `duplicate`, which trust ownership of an old timesheet more than the user's current access to the underlying project, activity, and customer.\n\n### Details\n\nThe issue affects the following operations:\n\n- `PATCH /api/timesheets/{id}/restart`\n- `PATCH /api/timesheets/{id}/duplicate`\n\nThe root cause is that authorization gives too much weight to the fact that the original timesheet belongs to the current user. In `src/Voter/TimesheetVoter.php`, the `*_own_timesheet` branch is evaluated before team-based access checks.\n\nThe restart/duplicate capability check also verifies only object visibility, not whether the current user still has team-based access to the referenced objects. \n\nIn `src/API/TimesheetController.php`, the restart flow copies the historical ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.58.0"]}],"null_published_at":"2026-11-01T19:14:01.600Z","source_updated_at":"2026-07-14T00:26:47.269Z","source_disclosed_at":"2026-07-14T00:04:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:10.696Z"},{"id":"NVI-00006782","kind":"vulnerability","title":"Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c6w6-57jj-62vh","CVE-2026-52822"],"plain_summary":"OSV carries this publisher advisory for kimai/kimai. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.58.0 for kimai/kimai. Confirm the publisher’s latest guidance.","source_ids":["sr-c2650922499cf62d4b50f813a7809811"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c2650922499cf62d4b50f813a7809811","url":"https://github.com/advisories/GHSA-c6w6-57jj-62vh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c6w6-57jj-62vh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.696Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c2650922499cf62d4b50f813a7809811"],"technology":"kimai/kimai","known_exclusions":[],"conditions_summary":"### Summary\n\nKimai 2.56.0 contains an authenticated authorization bypass in the timesheet `restart` and `duplicate` workflows. After a user loses access to a project, the user can still derive a new timesheet from one of their historical entries and create a new record under that now-unauthorized project and activity combination.\n\nThis is a permission revocation bypass with persistent write impact. The issue affects both `restart` and `duplicate`, which trust ownership of an old timesheet more than the user's current access to the underlying project, activity, and customer.\n\n### Details\n\nThe issue affects the following operations:\n\n- `PATCH /api/timesheets/{id}/restart`\n- `PATCH /api/timesheets/{id}/duplicate`\n\nThe root cause is that authorization gives too much weight to the fact that the original timesheet belongs to the current user. In `src/Voter/TimesheetVoter.php`, the `*_own_timesheet` branch is evaluated before team-based access checks.\n\nThe restart/duplicate capability check also verifies only object visibility, not whether the current user still has team-based access to the referenced objects. \n\nIn `src/API/TimesheetController.php`, the restart flow copies the historical ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.58.0"]}],"null_published_at":"2026-10-31T22:13:10.073Z","source_updated_at":"2026-07-14T00:26:47.269Z","source_disclosed_at":"2026-07-14T00:04:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:10.696Z"}],"next_cursor":null,"snapshot_revision":"42594"}