# CVE-2026-54206: TeamDavid: Server-Side Request Forgery (SSRF) via 'pathname' parameter in sending functionality

> Unauthenticated attackers can trigger SSRF via UNC paths to steal NTLM hashes or relay SMB connections, requiring disabling the feature or upgrading.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-9q86-rqgf-5jcm

## What is CVE-2026-54206?

CVE-2026-54206 is a medium-severity server-side request forgery vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tobit Laboratories AG TeamDavid's Webbox 's sending email, fax, SMS, etc. functionality accepts a 
@@INCLUDE command, which can be set to network locations using UNC paths
 (e.g., “\\Server\Share”). The server processes these paths without 
validation, resulting in outbound connection attempts to 
attacker-controlled SMB servers. This enables authenticated attackers to
 trigger the server to authenticate to arbitrary SMB endpoints, 
potentially exposing NTLM authentication information (such as NTLM 
hashes). If outbound connections to port 445 (SMB) are permitted, 
attackers can use this to conduct SMB relay or credential theft attacks.
 Exploitation of the “pathname” parameter is possible without 
authentication. This issue affects TeamDavid before Rollout 528.

Starting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-54206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54206 is a medium-severity server-side request forgery vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54206 in the wild and no public exploit code.

Affected product: Tobit Laboratories AG TeamDavid. 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-54206/ (Markdown: https://insights.sbomify.com/CVE-2026-54206/index.md)
```

## Sources

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

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