Is CVE-2026-49992 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49992 being exploited in the wild.

How severe is CVE-2026-49992?

Medium severity, with a CVSS score of 4, published 11 September 2026.

Which products and versions are affected?

Kimai <= 2.57.0; kimai/kimai (Packagist) <= 2.57.0, ECOSYSTEM:introduced=0,fixed=2.58.0.

Is there a fix for CVE-2026-49992?

Yes. kimai/kimai (Packagist): upgrade to 2.58.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-49992 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-49992?

Check whether you run Kimai or kimai/kimai (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49992: Kimai CSRF in team creation endpoints

Q: Which products and versions are affected?

Kimai <= 2.57.0; kimai/kimai (Packagist) <= 2.57.0, ECOSYSTEM:introduced=0,fixed=2.58.0.

Q: Is there a fix for CVE-2026-49992?

Yes. kimai/kimai (Packagist): upgrade to 2.58.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-49992 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-49992?

Check whether you run Kimai or kimai/kimai (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49992 · Severity: medium · CVSS 4 · Published 2026-09-11

Kimai, an open-source time-tracking application, contains a security flaw that allows unauthorized changes to team and permission structures. By tricking a logged-in administrator into clicking a malicious link, an attacker can force the system to create new teams or reassign project ownership. This could lead to unauthorized access to sensitive project data, reporting errors, and a breakdown of organizational access controls.

Technologies: Kimai, kimai/kimai (Packagist). Vendors: Kimai, Packagist.

Quick answers

Is CVE-2026-49992 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49992 being exploited in the wild.
How severe is CVE-2026-49992?: Medium severity, with a CVSS score of 4, published 11 September 2026.
Which products and versions are affected?: Kimai <= 2.57.0; kimai/kimai (Packagist) <= 2.57.0, ECOSYSTEM:introduced=0,fixed=2.58.0.
Is there a fix for CVE-2026-49992?: Yes. kimai/kimai (Packagist): upgrade to 2.58.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49992 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49992?: Check whether you run Kimai or kimai/kimai (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

kimai/kimai (Packagist): upgrade to 2.58.0 or later
```
composer require kimai/kimai:^2.58.0
```

Technical details

A Cross-Site Request Forgery (CSRF) vulnerability exists in Kimai versions up to 2.57.0 due to the use of GET requests for state-changing operations. Specifically, the endpoints for creating teams for projects, customers, and activities (/en/admin/project/{id}/create_team, etc.) perform persistent writes without proper CSRF protection. An attacker can exploit this by inducing an authenticated user with management permissions to visit a malicious URL. Successful exploitation allows the attacker to create or reuse teams, assign the victim as a team lead, and bind objects to those teams, effectively altering the application's authorization topology. The issue was resolved in version 2.58.0 by migrating these routes to POST endpoints.

Affected products

Kimai Kimai <= 2.57.0

Identifiers

CVE-2026-49992
GHSA-pgcc-vfmc-7cw5

Timeline

2026-06-03: disclosed: Initial disclosure to GitHub Advisory Database
2026-07-13: advisory: GitHub Advisory published and reviewed
2026-07-13: patched: Fix confirmed in version 2.58.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.