CVE-2026-52822: Kimai/kimai Improper Authorization Vulnerability

MODERATE
Advisory Identifier: GHSA-c6w6-57jj-62vh
CWE-862 CWE-285
Published
Advisory Summary

CVE-2026-52822 is a MODERATE improper authorization vulnerability (CWE-862: Missing Authorization) affecting Kimai/kimai libraries in the Packagist ecosystem. The issue involves improper authorization in kimai timesheet restart and duplicate allows new timesheets after project access revocation. Remediation is available by upgrading affected packages to version 2.58.0.

CVE-2026-52822 at a Glance

CVE Identifier CVE-2026-52822
GHSA Identifier GHSA-c6w6-57jj-62vh
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-862: Missing Authorization
Affected Product Kimai/kimai
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-52822

To remediate this vulnerability, upgrade all affected Kimai/kimai dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

kimai/kimai fixed: 2.58.0
Upgrade kimai/kimai to 2.58.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for kimai/kimai

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-52822, inspect your project dependencies for Kimai/kimai:

inspect dependencies for kimai/kimai

Analyze the terminal output to locate any version of Kimai/kimai in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.58.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Kimai/kimai, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Kimai 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. This 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. ### Details The issue affects the following operations: - `PATCH /api/timesheets/{id}/restart` - `PATCH /api/timesheets/{id}/duplicate` The 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. The restart/duplicate capability check also verifies only object visibility, not whether the current user still has team-based access to the referenced objects. In `src/API/TimesheetController.php`, the restart flow copies the historical `project` and `activity` into a new candidate timesheet. The duplicate flow similarly clones the historical record and saves it. In `src/Timesheet/TimesheetService.php`, creation of a new running entry still relies on `isGranted('start', $timesheet)`. For historical entries that belong to the current user, this logic can still succeed through the `*_own_timesheet` branch even after project access has been revoked. As a result, normal creation pages correctly stop offering the revoked project, but `restart` and `duplicate` can still create new records under it. The same weakness also affects the Web duplicate flow because the UI path ultimately calls the same save logic in `src/Controller/TimesheetAbstractController.php`: *A PoC was provided, but removed for security reasons.* ### Impact This vulnerability allows a user to keep writing new time entries into a project after project access has been revoked. That undermines administrative access-control changes and can pollute project time tracking, budget calculations, statistics, reports, and invoicing workflows. Because both `restart` and `duplicate` can reuse historical project/activity bindings, old timesheet records effectively become reusable capability tokens that survive later access-control changes. This is not a UI artifact or a caching problem: new database rows are persisted after revocation. # Solution The metoid `TimesheetVoter::canStart()` now checks team access for project and activity. This verification is used for new timesheets and also for the `duplication` and `restart` workflows. See [https://www.kimai.org/en/security/ghsa-c6w6-57jj-62vh](https://www.kimai.org/en/security/ghsa-c6w6-57jj-62vh) for more information.

CVE-2026-52822 Affected Kimai/kimai Versions

1 component(s)
Fixed Versions:
2.58.0
Product / Package Ecosystem Affected Versions Fixed Version
kimai/kimai
Packagist
< 2.58.0
2.58.0

References

Frequently Asked Questions

What is CVE-2026-52822?
CVE-2026-52822 is a security vulnerability in Kimai/kimai involving Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation under CWE-862: Missing Authorization.
Which Kimai/kimai versions are affected?
Affected versions include releases prior to 2.58.0 across affected packages: kimai/kimai.
What version fixes CVE-2026-52822?
Upgrading to 2.58.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is kimai/kimai affected?
Yes, kimai/kimai is affected in releases prior to 2.58.0. Upgrade your dependency to 2.58.0 or later.
What CWE is associated with CVE-2026-52822?
CVE-2026-52822 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Packagist dependencies for CVE-2026-52822?
Run the dependency tree command: 'inspect dependencies for kimai/kimai'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c6w6-57jj-62vh",
  "modified" : "2026-07-14T00:04:26Z",
  "published" : "2026-07-14T00:04:26Z",
  "aliases" : [ "CVE-2026-52822" ],
  "summary" : "Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation",
  "details" : "### 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 `project` and `activity` into a new candidate timesheet.\n\nThe duplicate flow similarly clones the historical record and saves it.\n\nIn `src/Timesheet/TimesheetService.php`, creation of a new running entry still relies on `isGranted('start', $timesheet)`.\n\nFor historical entries that belong to the current user, this logic can still succeed through the `*_own_timesheet` branch even after project access has been revoked. As a result, normal creation pages correctly stop offering the revoked project, but `restart` and `duplicate` can still create new records under it.\n\nThe same weakness also affects the Web duplicate flow because the UI path ultimately calls the same save logic in `src/Controller/TimesheetAbstractController.php`:\n\n*A PoC was provided, but removed for security reasons.*\n\n### Impact\n\nThis vulnerability allows a user to keep writing new time entries into a project after project access has been revoked. That undermines administrative access-control changes and can pollute project time tracking, budget calculations, statistics, reports, and invoicing workflows.\n\nBecause both `restart` and `duplicate` can reuse historical project/activity bindings, old timesheet records effectively become reusable capability tokens that survive later access-control changes. This is not a UI artifact or a caching problem: new database rows are persisted after revocation.\n\n# Solution\n\nThe metoid `TimesheetVoter::canStart()` now checks team access for project and activity. This verification is used for new timesheets and also for the `duplication` and `restart` workflows.\n\nSee [https://www.kimai.org/en/security/ghsa-c6w6-57jj-62vh](https://www.kimai.org/en/security/ghsa-c6w6-57jj-62vh) for more information.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "kimai/kimai"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.58.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.57.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kimai/kimai/security/advisories/GHSA-c6w6-57jj-62vh"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kimai/kimai"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285", "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-14T00:04:26Z",
    "nvd_published_at" : null
  }
}