CVE-2026-49992

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th 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
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Kimai is an open-source time tracking application. Versions prior to 2.58.0 contain authenticated cross-site request forgery issues in their default team creation shortcuts for projects, customers, and activities. These endpoints are exposed through GET routes and directly create or reuse a Team, add the current user as teamlead, and bind the target object to that team. As a result, an attacker can trick a logged-in user with the required permissions into visiting a malicious page and cause unauthorized changes to team, teamlead, and object-binding relationships. This is a real authorization-structure modification issue rather than a harmless UI shortcut. Version 2.58.0 patches the issue.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
0.2%
EPSS %ILE
11th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 13, 2026

Last Modified

September 23, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github.
Web page

CSRF attack allowed tricking logged-in users into creating teams and changing access – Kimai

https://www.kimai.org/en/security/ghsa-pgcc-vfmc-7cw5
GitHub advisoryMentions a patch (unverified)

CSRF in Kimai Default Team Creation Endpoints Allows Unauthorized Team and Permission Structure Changes · Advisory · kimai/kimai · GitHub

https://github.com/kimai/kimai/security/advisories/GHSA-pgcc-vfmc-7cw5

Vendor Advisories for CVE-2026-49992(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 10× in last 7d / 32× 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-13 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-01 13:51 UTCEG score recompute
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-09-28 09:27 UTCEG score recompute
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-09-23 19:06 UTCEG score recompute
  24. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-23 04:16 UTCEG score recompute
Show 17 more
  1. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-09-18 05:00 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-14 18:08 UTCEG score recompute
  7. 2026-09-14 16:20 UTCEG score recompute
  8. 2026-09-14 06:19 UTCEG score recompute
  9. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-09-13 07:57 UTCEG score recompute
  11. 2026-09-11 23:11 UTCEG score recompute
  12. 2026-09-11 21:39 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  13. 2026-09-11 21:38 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  14. 2026-08-01 11:49 UTCEG score recompute
  15. 2026-07-26 11:50 UTCEG score recompute
  16. 2026-07-23 03:18 UTCEG score recompute
  17. 2026-07-14 00:09 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-49992?
CVE-2026-49992 is a medium-severity vulnerability; its CVE record was published on July 13, 2026. Kimai is an open-source time tracking application. Versions prior to 2.58.0 contain authenticated cross-site request forgery issues in their default team creation shortcuts for projects, customers, and activities. These endpoints are exposed through GET routes and directly create or reuse a Team,…
When was the CVE record for CVE-2026-49992 published?
The CVE record for CVE-2026-49992 was published on July 13, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-49992 actively exploited?
CVE-2026-49992 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49992?
CVE-2026-49992 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49992?
A fix for CVE-2026-49992 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49992 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-49992

Explore →

Is Your Infrastructure Affected by CVE-2026-49992?

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

Book a Demo →Browse All CVEs