CVE-2026-40029

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

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

parseusbs before 1.9 contains an OS command injection vulnerability in parseUSBs.py where LNK file paths are passed unsanitized into an os.popen() shell command, allowing arbitrary command execution via crafted .lnk filenames containing shell metacharacters. An attacker can craft a .lnk filename with embedded shell metacharacters that execute arbitrary commands on the forensic examiner's machine during USB artifact parsing.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
52.6%
KEV
Not listed

Published

April 8, 2026

Last Modified

June 23, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

parseusbs < 1.9 Command Injection via Crafted LNK Filename | Advisories | VulnCheck

https://www.vulncheck.com/advisories/parseusbs-command-injection-via-crafted-lnk-filename
generic

Sentinel: Security Review Program | Mobasi

https://mobasi.ai/sentinel
github_pr

Fix command injection in volume and LNK parsing

Fix merged in khyrenz/parseusbs PR #10 on 2026-02-08 — awaiting tagged release

https://github.com/khyrenz/parseusbs/pull/10
github_commit

commit 99f05996494e (khyrenz/parseusbs)

Fix landed in khyrenz/parseusbs commit 99f05996494e — awaiting tagged release

https://github.com/khyrenz/parseusbs/commit/99f05996494e7e41ea0c7e13145ba20eb793e46b

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-40029?
CVE-2026-40029 is a high vulnerability published on April 8, 2026. parseusbs before 1.9 contains an OS command injection vulnerability in parseUSBs.py where LNK file paths are passed unsanitized into an os.popen() shell command, allowing arbitrary command execution via crafted .lnk filenames containing shell metacharacters. An attacker can craft a .lnk filename…
When was CVE-2026-40029 disclosed?
CVE-2026-40029 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40029 actively exploited?
CVE-2026-40029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40029?
CVE-2026-40029 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-40029?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40029, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-40029?

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

Start Free Scan →Browse All CVEs