CVE-2026-40025

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.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 an out-of-bounds read vulnerability in the APFS filesystem keybag parser where the wrapped_key_parser class follows attacker-controlled length fields without bounds checking, causing heap reads past the allocated buffer. An attacker can craft a malicious APFS disk image that triggers information disclosure or crashes when processed by any Sleuth Kit tool that parses APFS volumes.

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

Published

April 8, 2026

Last Modified

July 25, 2026

Advisory Details (4)

Auto-updated Jul 25, 2026
Patch available. Sources: github_commit, github_pr.
generic

Sleuth Kit APFS Keybag Parser Out-of-Bounds Read | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sleuth-kit-apfs-keybag-parser-out-of-bounds-read
generic

Sentinel: Security Review Program | Mobasi

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

Fix overflow bug in APFS code. Reported by Mobasi. Also brought in some build changes from develop and fixed some build issues.

Patch available: sleuthkit/sleuthkit sleuthkit-4.15.0 (PR #3444 merged 2026-03-01)

https://github.com/sleuthkit/sleuthkit/pull/3444
github_commit Patch Available

commit 8b9c9e7d493b (sleuthkit/sleuthkit)

Patch available: sleuthkit/sleuthkit sleuthkit-4.15.0 (contains commit 8b9c9e7d493b)

https://github.com/sleuthkit/sleuthkit/commit/8b9c9e7d493bd68624f3b1a3963edd45c3ff7611

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

Frequently asked(5)

What is CVE-2026-40025?
CVE-2026-40025 is a medium vulnerability published on April 8, 2026. The Sleuth Kit through 4.14.0 contains an out-of-bounds read vulnerability in the APFS filesystem keybag parser where the wrappedkeyparser class follows attacker-controlled length fields without bounds checking, causing heap reads past the allocated buffer. An attacker can craft a malicious APFS…
When was CVE-2026-40025 disclosed?
CVE-2026-40025 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-40025 actively exploited?
CVE-2026-40025 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-40025?
CVE-2026-40025 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-40025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40025, 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-40025

Explore →

Is Your Infrastructure Affected by CVE-2026-40025?

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

Start Free Scan →Browse All CVEs