Skip to content
Applications

CVE-2026-54203

9.2
Critical
EPSS 0.32%Aug 7, 2026

Unauthenticated memory leak in Tobit TeamDavid exposes sensitive data including passwords.

common questions

Is CVE-2026-54203 being exploited?

Not confirmed. CVE-2026-54203 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-54203?

CVE-2026-54203 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-54203?

Not known from our data. No patch reference has been recorded for CVE-2026-54203, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-54203 affect?

CVE-2026-54203 affects Tobit Laboratories TeamDavid Webbox (through Rollout 524). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54203?

Block access to /.well-known/mta-sts, restrict/segment devices, rotate credentials and apply vendor patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Tobit Laboratories TeamDavid Webbox (through Rollout 524)
impact

Unauthenticated remote memory leak via /.well-known/mta-sts discloses memory including user passwords — enables credential theft and account takeover.

action required

Immediate action required

affected versions
Tobit Laboratories AG TeamDavid
  • affected< Rollout 528

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free