CVE-2026-8993: Ditec a.s D.Launcher 2 · Injection
Affects Ditec a.s D.Launcher 2Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.0.7 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Ditec a.s D.Launcher 2 to 2.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Ditec a.s.D.Launcher 2 | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should exercise caution when opening URLs from untrusted sources, especially those invoking custom URL handlers related to D.Launcher 2. No official mitigation or temporary fix has been documented.
Description
D.Launcher 2 component of Slovak eID client ecosystem contains Improper URL Handler Processing vulnerability. Application registers multiple custom URL handlers that could be exploited to initiate full NTLM autentication or SMB connection to attacker infrastructure and to conduct SSRF (Server Side Request Forgery) attacks. User interaction is required as potential victim needs to open a specially crafted URL.