CVE-2026-66415

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. The CNA's CVSS baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Leantime 3.6.2 contains a server-side request forgery and local file inclusion vulnerability that allows authenticated attackers to read internal resources by passing unsanitized user-supplied filenames to file_get_contents() in the Blueprints::import() method without path validation. Attackers can submit crafted filenames containing URL wrappers or path traversal sequences through the JSON-RPC API endpoint to access cloud metadata services or read arbitrary files from the server filesystem.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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 30, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Jul 30, 2026
Fix referenced — no release confirmed yet. Sources: github_pr, github.
Web page

Leantime Server-Side Request Forgery and Local File Inclusion in Blueprints::import() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/leantime-server-side-request-forgery-and-local-file-inclusion-in-blueprints-import
Web page

GitHub - Leantime/leantime: Leantime is a goals focused project management system for non-project managers. Building with ADHD, Autism, and dyslexia in mind. · GitHub

https://github.com/Leantime/leantime
GitHub advisoryMentions a patch (unverified)

SSRF + LFI in Leantime Blueprints::import() — CWE-918 · Advisory · javokhir-sec/CVE-PoC-Hub · GitHub

https://github.com/javokhir-sec/CVE-PoC-Hub/security/advisories/GHSA-gphg-6h4g-mg22
GitHub pull request

fix: validate file path in Blueprints::import() to prevent SSRF/LFI (CWE-918)

Fix merged in Leantime/leantime PR #3656 on 2026-07-25 — awaiting tagged release

https://github.com/Leantime/leantime/pull/3656

Vendor Advisories for CVE-2026-66415(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 61× 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.

Showing the most recent 100 of 244 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-18 03:21 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  9. 2026-10-13 10:56 UTCEG score recompute
  10. 2026-10-13 10:56 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  11. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-10-12 15:46 UTCEG score recompute
  13. 2026-10-11 19:31 UTCEG score recompute
  14. 2026-10-11 16:46 UTCEG score recompute
  15. 2026-10-11 14:07 UTCEG score recompute
  16. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  21. 2026-10-06 23:52 UTCEG score recompute
  22. 2026-10-06 23:52 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-10-05 20:00 UTCEG score recompute
  25. 2026-10-05 19:59 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
Show 75 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  2. 2026-10-04 23:56 UTCEG score recompute
  3. 2026-10-04 23:56 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  4. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  5. 2026-10-04 06:38 UTCEG score recompute
  6. 2026-10-04 06:38 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  7. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  9. 2026-10-02 16:57 UTCEG score recompute
  10. 2026-10-02 16:57 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  11. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-10-01 14:30 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  13. 2026-10-01 02:53 UTCEG score recompute
  14. 2026-10-01 02:53 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  16. 2026-09-29 06:53 UTCEG score recompute
  17. 2026-09-29 06:53 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  18. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-09-28 06:37 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  20. 2026-09-27 19:00 UTCEG score recompute
  21. 2026-09-27 19:00 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  23. 2026-09-25 04:56 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  24. 2026-09-24 15:00 UTCEG score recompute
  25. 2026-09-24 15:00 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  26. 2026-09-24 09:06 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  27. 2026-09-23 21:29 UTCEG score recompute
  28. 2026-09-23 21:29 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  29. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-09-23 02:49 UTCEG score recompute
  31. 2026-09-23 02:49 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  32. 2026-09-22 15:12 UTCEG score recompute
  33. 2026-09-22 15:12 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  34. 2026-09-20 21:15 UTCEG score recompute
  35. 2026-09-20 21:15 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  36. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-09-19 23:46 UTCEG score recompute
  38. 2026-09-19 23:46 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  39. 2026-09-19 04:15 UTCEG score recompute
  40. 2026-09-19 04:15 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-09-18 13:35 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  43. 2026-09-18 01:22 UTCEG score recompute
  44. 2026-09-18 01:22 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  45. 2026-09-17 01:28 UTCEG score recompute
  46. 2026-09-17 01:28 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  47. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-09-16 05:34 UTCEG score recompute
  49. 2026-09-16 05:34 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  50. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  51. 2026-09-15 03:17 UTCEG score recompute
  52. 2026-09-15 03:17 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  53. 2026-09-14 14:14 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  54. 2026-09-14 01:10 UTCEG score recompute
  55. 2026-09-14 01:10 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  56. 2026-09-13 13:34 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  57. 2026-09-13 01:57 UTCEG score recompute
  58. 2026-09-13 01:57 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  59. 2026-09-12 14:19 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  60. 2026-09-12 02:42 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  61. 2026-09-11 14:59 UTCEG score recompute
  62. 2026-09-11 14:59 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  63. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  65. 2026-09-11 02:45 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  66. 2026-09-10 15:08 UTCEG score recompute
  67. 2026-09-10 15:08 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  68. 2026-09-10 03:31 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  69. 2026-09-09 07:13 UTCEG score recompute
  70. 2026-09-09 07:12 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  71. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  72. 2026-09-07 19:50 UTCEG score recompute
  73. 2026-09-07 19:50 UTCGHSA enrichmentGHSA-rfxf-9pcf-q3rq · GitHub severity HIGH · GitHub CVSS 8.5
  74. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  75. 2026-09-06 18:16 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-66415?
CVE-2026-66415 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Leantime 3.6.2 contains a server-side request forgery and local file inclusion vulnerability that allows authenticated attackers to read internal resources by passing unsanitized user-supplied filenames to filegetcontents() in the Blueprints::import() method without path validation. Attackers can…
When was CVE-2026-66415 made public?
CVE-2026-66415 was made public on July 30, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-66415 actively exploited?
CVE-2026-66415 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66415?
CVE-2026-66415 has a CVSS base score of 8.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-66415?
A fix for CVE-2026-66415 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-66415 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66415

Explore →

Is Your Infrastructure Affected by CVE-2026-66415?

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