CVE-2026-52824

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.3% (70th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Kimai is an open-source time tracking application. Prior to 2.58.0, the official Docker image sets APP_SECRET to the public value change_this_to_something_unique in Dockerfile, and .docker/entrypoint.sh neither replaces nor rejects that value before Symfony uses it as kernel.secret. An unauthenticated attacker who reaches a deployment that did not override APP_SECRET, knows a username, correctly guesses the account ID associated with that username, and targets an account without active two-factor authentication can forge HMAC-protected authentication artifacts, including KIMAI_REMEMBER cookies and login links, to access the account without its password. The updated entrypoint generates and persists a random secret when no safe operator-provided value exists. This issue is fixed in version 2.58.0.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation1.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
Web page

Docker installations using the default secret key could be taken over by attackers – Kimai

https://www.kimai.org/en/security/ghsa-jr9p-4h4j-6c58
GitHub advisoryMentions a patch (unverified)

Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover · Advisory · kimai/kimai · GitHub

https://github.com/kimai/kimai/security/advisories/GHSA-jr9p-4h4j-6c58
GitHub release Patch Available

2.58.0

Patch available: kimai/kimai 2.58.0

https://github.com/kimai/kimai/releases/tag/2.58.0
GitHub pull request Patch Available

Release 2.58

Patch available: kimai/kimai 2.58.0 (PR #5952 merged 2026-05-25)

https://github.com/kimai/kimai/pull/5952
GitHub commit Patch Available

commit 31a8f887a5cd (kimai/kimai)

Patch available: kimai/kimai 2.58.0 (contains commit 31a8f887a5cd)

https://github.com/kimai/kimai/commit/31a8f887a5cda517db7b4320a7ad997c87d08601

Vendor Advisories for CVE-2026-52824(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
kimai/kimai0.1 ... 2.9.0 (203 versions)
  • every version up to 2.58.0: fixed in 2.58.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-14 02:00 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  3. 2026-10-12 22:18 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  5. 2026-10-12 15:58 UTCEG score recompute
  6. 2026-10-11 19:41 UTCEG score recompute
  7. 2026-10-11 16:56 UTCEG score recompute
  8. 2026-10-11 14:19 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  20. 2026-09-30 18:11 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  22. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  24. 2026-09-28 09:25 UTCEG score recompute
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
Show 18 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  2. 2026-09-26 00:27 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  3. 2026-09-24 09:58 UTCEG score recompute
  4. 2026-09-23 17:53 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  5. 2026-09-23 04:16 UTCEG score recompute
  6. 2026-09-18 19:28 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  7. 2026-09-18 04:59 UTCEG score recompute
  8. 2026-09-16 18:27 UTCEG score recompute
  9. 2026-09-16 17:53 UTCEG score recompute
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-15 11:29 UTCEG score recompute
  13. 2026-09-15 10:50 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
  14. 2026-09-15 10:47 UTCMITRE cvelistV5CVSS v3 → 9.1 · CVSS v4 → 9.1
  15. 2026-07-31 22:10 UTCEG score recompute
  16. 2026-07-26 11:50 UTCEG score recompute
  17. 2026-07-23 03:19 UTCEG score recompute
  18. 2026-07-14 00:25 UTCEG score recompute

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-52824.yaml
    Published Jul 21, 2026

    Kimai <= 2.57.0 - Default APP_SECRET Authentication Bypass

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-52824?
CVE-2026-52824 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Kimai is an open-source time tracking application. Prior to 2.58.0, the official Docker image sets APPSECRET to the public value changethistosomethingunique in Dockerfile, and .docker/entrypoint.sh neither replaces nor rejects that value before Symfony uses it as kernel.secret. An unauthenticated…
When was the CVE record for CVE-2026-52824 published?
The CVE record for CVE-2026-52824 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-52824 actively exploited?
CVE-2026-52824 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52824?
CVE-2026-52824 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52824?
A fix for CVE-2026-52824 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52824 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52824

Explore →

Is Your Infrastructure Affected by CVE-2026-52824?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs