CVE-2026-8398
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA supply chain attack compromised the official installation packages of DAEMON Tools Lite (Windows versions 12.5.0.2421 through 12.5.0.2434), distributed from the legitimate website daemon-tools.cc between approximately April 8, 2026, and May 5, 2026. Attackers gained unauthorized access to the vendor's (AVB Disc Soft) build or distribution infrastructure and trojanized three binaries: DTHelper.exe, DiscSoftBusServiceLite.exe, and DTShellHlp.exe. These files were digitally signed with the legitimate AVB Disc Soft code-signing certificate, allowing the malicious installers to appear trustworthy and bypass signature-based detection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a supply chain attack where official DAEMON Tools Lite installers (versions 12.5.0.2421-12.5.0.2434) were compromised between April 8 and May 5, 2026. Attackers gained unauthorized access to the vendor's build/distribution infrastructure and trojanized three binaries (DTHelper.exe, DiscSoftBusServiceLite.exe, DTShellHlp.exe). The malicious installers were digitally signed with the legitimate AVB Disc Soft code-signing certificate, allowing them to bypass signature-based detection and appear trustworthy.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed DAEMON Tools Lite versionOpen Windows Settings > Apps & Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Daemon Tools*"} | Select-Object Name, Version', or check the version in the program's About/Help sectionAffected if Installed version is 12.5.0.2421, 12.5.0.2422, 12.5.0.2423, 12.5.0.2424, 12.5.0.2425, 12.5.0.2426, 12.5.0.2427, 12.5.0.2428, 12.5.0.2429, 12.5.0.2430, 12.5.0.2431, 12.5.0.2432, 12.5.0.2433, or 12.5.0.2434 (the range 12.5.0.2421-12.5.0.2434)
-
Verify trojanized binary presenceCheck program installation directory for DTHelper.exe, DiscSoftBusServiceLite.exe, and DTShellHlp.exe - these were the three binaries trojanized in this supply chain attackAffected if Any of these three executables exist in the DAEMON Tools installation folder and the version falls within the affected range
-
Confirm installation date windowCheck Windows Event Log for MSI installer events, or check file creation timestamps on the DAEMON Tools installation files, or check 'wmic product where "name like '%Daemon Tools%'" get installdate'Affected if DAEMON Tools Lite was installed or updated between April 8, 2026 and May 5, 2026 (the known compromise window)
-
Verify digital signature anomalyRight-click each suspicious executable > Properties > Digital Signatures tab - the malware carried a legitimate AVB Disc Soft code-signing certificate, so signature validation alone would not detect this; focus on version/date correlation insteadAffected if Binaries are signed but version falls within the known malicious version range
A user is affected if DAEMON Tools Lite versions 12.5.0.2421 through 12.5.0.2434 were installed during the April 8 to May 5, 2026 compromise window, as the installers were trojanized with malware despite carrying a legitimate code-signing certificate.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataOrganizations must immediately identify and remove any installations of DAEMON Tools Lite versions 12.5.0.2421 through 12.5.0.2434, conduct forensic analysis for signs of compromise, and reinstall only from verified clean sources after the vendor confirms the supply chain issue is resolved. Review code-signing certificate management practices and implement additional integrity verification for software deployments.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8398 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8398 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data