# CVE-2026-54201: TeamDavid: Missing Authorization

> Attackers can access sensitive log files without authentication, exposing internal details that may aid further attacks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **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-r8f9-gq2j-8hf4

## What is CVE-2026-54201?

CVE-2026-54201 is a medium-severity missing authorization 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  does not enforce authentication or authorization checks
 when serving these log files. As a result, attackers can obtain 
sensitive error information or internal application details, potentially
 aiding in further attacks. 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-862 (Missing Authorization)

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


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

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

## Is CVE-2026-54201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54201 is a medium-severity missing authorization 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-54201 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-54201/ (Markdown: https://insights.sbomify.com/CVE-2026-54201/index.md)
```

## Sources

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

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