# CVE-2026-54210: TeamDavid: Buffer Overflow in file names of file upload functionalities

> Unauthenticated attackers can cause server crashes or potentially execute code via buffer overflow in file upload filenames.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-rghw-4g53-4wwv

## What is CVE-2026-54210?

CVE-2026-54210 is a critical memory corruption vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tobit Laboratories AG TeamDavid's Webbox application implements various file upload functionalities that are 
vulnerable to a buffer overflow condition. By specifying an excessively 
long filename in a file upload request, an unauthenticated attacker can 
trigger a crash of the server, resulting in a denial of service. 
Depending on the stack state or if a stack canary can be disclosed 
through another vulnerability, this buffer overflow could potentially be
 exploited for remote code execution, leading to full compromise of the 
server. 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-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-54210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54210 is a critical memory corruption vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54210 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-54210/ (Markdown: https://insights.sbomify.com/CVE-2026-54210/index.md)
```

## Sources

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

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