Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover (CVE-2026-52824)
The official Kimai Docker image shipped with a default APP_SECRET environment variable set to a known static value. This default secret was not overridden or validated at startup, allowing attackers to forge HMAC-signed cookies and login links. This enables unauthenticated attackers to take over any account, including super_admin, if they know the username and can guess the user ID, provided the account does not have active two-factor authentication. The issue affects Kimai versions prior to 2.58.0. The vendor has updated the entrypoint script to generate a random APP_SECRET at startup, removed the default static secret from the Dockerfile, and improved login link entropy to mitigate the risk.
AI Analysis
Technical Summary
The Kimai Docker image set APP_SECRET to a default static value 'change_this_to_something_unique' which is used as the Symfony kernel.secret for HMAC signing of authentication cookies, login links, password reset URLs, and CSRF tokens. Because the Docker entrypoint did not override or validate this secret, any deployment using the default secret allowed unauthenticated attackers to forge authentication tokens and login links. User IDs are sequential and visible, enabling attackers to guess valid user IDs and impersonate any user without 2FA. The vulnerability affects all Kimai versions prior to 2.58.0. The vendor fixed this by removing the default secret, generating a random APP_SECRET at container startup, and increasing login link entropy.
Potential Impact
An unauthenticated attacker can forge authentication cookies and login links to fully compromise any user account, including super_admin, on Kimai instances deployed with the official Docker image without a custom APP_SECRET. This allows complete account takeover and bypass of authentication protections if two-factor authentication is not enabled. The vulnerability exposes all affected versions prior to 2.58.0 to remote compromise via the internet.
Mitigation Recommendations
The vendor has released an updated Docker image and entrypoint script that generates a random APP_SECRET at startup and removes the default static secret. Users should upgrade to Kimai version 2.58.0 or later and ensure the APP_SECRET environment variable is set to a unique, random value. The updated entrypoint script automatically manages this secret. Additionally, enabling two-factor authentication on accounts mitigates the risk of takeover. Check the vendor advisory at https://www.kimai.org/en/security/ghsa-jr9p-4h4j-6c58 for the latest remediation details.
Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover (CVE-2026-52824)
Description
The official Kimai Docker image shipped with a default APP_SECRET environment variable set to a known static value. This default secret was not overridden or validated at startup, allowing attackers to forge HMAC-signed cookies and login links. This enables unauthenticated attackers to take over any account, including super_admin, if they know the username and can guess the user ID, provided the account does not have active two-factor authentication. The issue affects Kimai versions prior to 2.58.0. The vendor has updated the entrypoint script to generate a random APP_SECRET at startup, removed the default static secret from the Dockerfile, and improved login link entropy to mitigate the risk.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Kimai Docker image set APP_SECRET to a default static value 'change_this_to_something_unique' which is used as the Symfony kernel.secret for HMAC signing of authentication cookies, login links, password reset URLs, and CSRF tokens. Because the Docker entrypoint did not override or validate this secret, any deployment using the default secret allowed unauthenticated attackers to forge authentication tokens and login links. User IDs are sequential and visible, enabling attackers to guess valid user IDs and impersonate any user without 2FA. The vulnerability affects all Kimai versions prior to 2.58.0. The vendor fixed this by removing the default secret, generating a random APP_SECRET at container startup, and increasing login link entropy.
Potential Impact
An unauthenticated attacker can forge authentication cookies and login links to fully compromise any user account, including super_admin, on Kimai instances deployed with the official Docker image without a custom APP_SECRET. This allows complete account takeover and bypass of authentication protections if two-factor authentication is not enabled. The vulnerability exposes all affected versions prior to 2.58.0 to remote compromise via the internet.
Mitigation Recommendations
The vendor has released an updated Docker image and entrypoint script that generates a random APP_SECRET at startup and removes the default static secret. Users should upgrade to Kimai version 2.58.0 or later and ensure the APP_SECRET environment variable is set to a unique, random value. The updated entrypoint script automatically manages this secret. Additionally, enabling two-factor authentication on accounts mitigates the risk of takeover. Check the vendor advisory at https://www.kimai.org/en/security/ghsa-jr9p-4h4j-6c58 for the latest remediation details.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jr9p-4h4j-6c58
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-52824"]
- Ecosystems
- ["Packagist"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 4.0
Threat ID: 6a55ff8868715ace432f4648
Added to database: 07/14/2026, 09:21:12 UTC
Last enriched: 07/14/2026, 09:44:27 UTC
Last updated: 07/31/2026, 12:27:30 UTC
Views: 71
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.