Kimai is an open-source time tracking application. Versions prior to 2.58.0 contain a server-side request forgery vulnerability in their invoice PDF preview and generation workflow. If an attacker can control Markdown content that is later rendered into an invoice PDF, such as Customer.invoiceText, the server-side PDF renderer will fetch remote image URLs embedded in Markdown image syntax. This allows the application server to issue outbound requests to attacker-controlled or internal targets during PDF rendering. The behavior can be used for internal network probing, server-side reachability checks, and potentially follow-on exploitation depending on deployment environment and accessible internal services. Version 2.58.0 patches the issue.
CVE-2026-49865
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
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 computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
September 14, 2026
Advisory Details (1)
Auto-updated Sep 11, 2026Server-Side Request Forgery in Kimai Invoice PDF Rendering via Markdown Image URLs · Advisory · kimai/kimai · GitHub
https://github.com/kimai/kimai/security/advisories/GHSA-pj8j-p4g4-4vw8Vendor Advisories for CVE-2026-49865(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kimai/kimai | 0.1 ... 2.9.0 (203 versions) | 2.58.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:18 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 20:27 UTCEG score recompute
- 2026-09-14 20:16 UTCEG score recompute
- 2026-09-14 06:59 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:12 UTCEG score recompute
- 2026-09-11 21:24 UTCEG score recompute
- 2026-09-11 21:14 UTCEG score recompute▲ 5.30
- 2026-09-11 21:13 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
- 2026-08-01 05:10 UTCEG score recompute
- 2026-07-26 12:11 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-10 16:14 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-49865?
When was CVE-2026-49865 disclosed?
Is CVE-2026-49865 actively exploited?
What is the CVSS score of CVE-2026-49865?
How do I remediate CVE-2026-49865?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49865
Is Your Infrastructure Affected by CVE-2026-49865?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.