Skip to main content
EPSS 0.3%top 85%

Kimai (kimai/kimai) through 2.65.0 contains a business logic / improper authorization vulnerability in the default team creation endpoints. (CVE-2026-84807)

0
Medium
Published: 09/02/2026 (09/02/2026, 12:31:31 UTC)
Source: GCVE Database

Description

Kimai through version 2.65.0 has a business logic vulnerability in its default team creation endpoints. Authenticated users with project permission-management rights can exploit this flaw to gain unauthorized team-lead privileges by creating or using a customer, project, or activity with a name matching an existing team. This occurs because the endpoints reuse existing teams of the same name and add the user as teamlead without proper authorization checks. The issue is fixed in version 2.65.0.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected software

Affected versions
<2.65.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/08/2026, 02:39:26 UTC

Technical Analysis

Kimai versions up to 2.65.0 contain a business logic and improper authorization vulnerability (CWE-266) in the POST /api/customers/{id}/team, POST /api/projects/{id}/team, and POST /api/activities/{id}/team endpoints. An authenticated user with project permission-management privileges can create or reference a customer, project, or activity named identically to an existing team. The endpoints then reuse the existing team and add the user as a teamlead without verifying authorization to manage that team, allowing unauthorized elevation to team-lead (administration) rights. This vulnerability is fixed in version 2.65.0.

Potential Impact

An attacker with authenticated project permission-management privileges can escalate their access to gain unauthorized team-lead rights over existing teams. This could allow administrative control over team resources that the attacker should not manage. The impact is limited to confidentiality and integrity with no availability impact reported. The CVSS 3.1 base score is 5.4 (medium severity).

Mitigation Recommendations

Upgrade Kimai to version 2.65.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Since this is not a cloud service, users must apply the update themselves.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-p3c7-g2jr-3m35
Osv Schema Version
1.4.0
Aliases
["CVE-2026-84807"]
Database Specific Severity
MODERATE
Cvss Version
3.1

Threat ID: 6a98451eacd9273b496a9bba

Added to database: 09/02/2026, 15:47:42 UTC

Last enriched: 09/08/2026, 02:39:26 UTC

Last updated: 10/16/2026, 06:48:19 UTC

Views: 26

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses