# CVE-2026-8993: Improper URL Handler Processing in D.Launcher 2 enables NTLM Credential Disclosure and SSRF attacks

> Attackers can exploit improper URL handlers in D.Launcher 2 to steal NTLM credentials and perform SSRF attacks via crafted links.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-qh4g-88ff-qrg3

## What is CVE-2026-8993?

CVE-2026-8993 is a medium-severity server-side request forgery vulnerability in Ditec a.s. D.Launcher 2, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-1395 (Dependency on Vulnerable Third-Party Component)

## Which versions are affected by CVE-2026-8993?


## How do I fix CVE-2026-8993?

No fix has been published for CVE-2026-8993 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8993 being exploited?

There is no known exploitation of CVE-2026-8993 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8993 and fix it if it is affected.

What it is: CVE-2026-8993 is a medium-severity server-side request forgery vulnerability in Ditec a.s. D.Launcher 2, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-8993 in the wild and no public exploit code.

Affected product: Ditec a.s. D.Launcher 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8993/ (Markdown: https://insights.sbomify.com/CVE-2026-8993/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8993
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8993
- OSV: https://osv.dev/vulnerability/CVE-2026-8993

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8993/
Summaries are generated and may contain mistakes; the official description above is the record.