CVE-2026-40024

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-09. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Sleuth Kit through 4.14.0 contains a path traversal vulnerability in tsk_recover that allows an attacker to write files to arbitrary locations outside the intended recovery directory via crafted filenames or directory paths with path traversal sequences in a filesystem image. An attacker can craft a malicious filesystem image with embedded /../ sequences in filenames that, when processed by tsk_recover, writes files outside the output directory, potentially achieving code execution by overwriting shell configuration or cron entries.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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 computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

April 8, 2026

Last Modified

July 25, 2026

Advisory Details (3)

Auto-updated Jun 15, 2026
Patch available. Sources: github_commit.
generic

Sleuth Kit tsk_recover Path Traversal | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sleuth-kit-tsk-recover-path-traversal
generic

Sentinel: Security Review Program | Mobasi

https://mobasi.ai/sentinel
github_commit Patch Available

commit a3f96b3bc36a (sleuthkit/sleuthkit)

Patch available: sleuthkit/sleuthkit sleuthkit-4.15.0 (contains commit a3f96b3bc36a)

https://github.com/sleuthkit/sleuthkit/commit/a3f96b3bc36a8bb1a00c297f77110d4a6e7dd31b

Vendor Advisories for CVE-2026-40024(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
sleuthkit4.10.1+dfsg-1 ... 4.14.0+dfsg-1 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
sleuthkit4.11.1+dfsg-1 ... 4.14.0+dfsg-1 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
sleuthkit4.12.1+dfsg-3, 4.14.0+dfsg-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sleuthkit4.12.1+dfsg-3, 4.14.0+dfsg-1——

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 203 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40024?
CVE-2026-40024 is a high vulnerability published on April 8, 2026. The Sleuth Kit through 4.14.0 contains a path traversal vulnerability in tskrecover that allows an attacker to write files to arbitrary locations outside the intended recovery directory via crafted filenames or directory paths with path traversal sequences in a filesystem image. An attacker can…
When was CVE-2026-40024 disclosed?
CVE-2026-40024 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40024 actively exploited?
CVE-2026-40024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.8% of all scored CVEs.
What is the CVSS score of CVE-2026-40024?
CVE-2026-40024 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-40024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40024, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-40024?

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

Start Free Scan →Browse All CVEs