Is CVE-2026-80200 exploited in the wild?

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

How severe is CVE-2026-80200?

Medium severity, with a CVSS score of 4.7, published 26 August 2026.

Which products and versions are affected?

Kimai before 2.53.0; kimai/kimai (Packagist) ECOSYSTEM:introduced=0,fixed=2.53.0.

Is there a fix for CVE-2026-80200?

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

How is CVE-2026-80200 attacked?

It is attacked over the network.

Am I affected by CVE-2026-80200?

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-80200: Kimai open redirect in SAML authentication handler

CVE-2026-80200 · Severity: medium · CVSS 4.7 · Published 2026-08-26

Kimai is a time-tracking and project management web application that supports SAML-based single sign-on authentication. An attacker with access to a SAML identity provider can craft a malicious redirect that sends authenticated users to an attacker-controlled website after they log in, enabling credential theft or phishing attacks. This requires the victim to initiate login through an IdP-initiated SSO flow and the attacker to have control over the SAML identity provider configuration.

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

Quick answers

Is CVE-2026-80200 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-80200 being exploited in the wild.
How severe is CVE-2026-80200?: Medium severity, with a CVSS score of 4.7, published 26 August 2026.
Which products and versions are affected?: Kimai before 2.53.0; kimai/kimai (Packagist) ECOSYSTEM:introduced=0,fixed=2.53.0.
Is there a fix for CVE-2026-80200?: Yes. kimai/kimai (Packagist): upgrade to 2.53.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-80200 attacked?: It is attacked over the network.
Am I affected by CVE-2026-80200?: 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.53.0 or later
```
composer require kimai/kimai:^2.53.0
```

Technical details

The vulnerability is an open redirect (CWE-601) in the SAML authentication success handler (src/Saml/Security/SamlAuthenticationSuccessHandler.php) where the RelayState POST parameter is accepted as a redirect destination without validating the host or scheme. The vulnerable code only checks that RelayState does not equal the configured login_path, allowing any external URL to be used as a redirect target. An attacker with IdP access can supply a malicious RelayState value in an IdP-initiated SSO flow to redirect users post-authentication. The vulnerability was patched in version 2.53.0, which validates RelayState to ensure it contains no host/port, does not start with //, and if it contains a host, that host matches the current request host.

Affected products

Kimai Kimai before 2.53.0

Identifiers

CVE-2026-80200
GHSA-3jp4-mhh4-gcgr

Timeline

2026-04-11: disclosed
2026-04-11: patched: Fixed in version 2.53.0
2026-08-26: advisory

References

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