# CVE-2025-15682: Unauthenticated Resource Exhaustion

> Unauthenticated attackers can exhaust storage on TBEA TLogger devices by sending PUT requests that create persistent files, causing denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/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:** 10 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-3xp4-p2g8-p4gx

## What is CVE-2025-15682?

CVE-2025-15682 is a high-severity denial of service vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation), published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TBEA TLogger V2.1.0.0B0.0.0.0 contains an unauthenticated resource exhaustion vulnerability in its web server. An unauthenticated remote attacker can send PUT requests to the /tmp/ endpoint, causing the web server to create persistent files containing attacker-controlled data under /opt/myapp/webserver/. The generated files are not removed because the web server attempts to move them into a non-existent directory. Repeated requests can therefore exhaust available storage and cause a denial-of-service condition.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-15682?


## How do I fix CVE-2025-15682?

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

## Is CVE-2025-15682 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15682 and fix it if it is affected.

What it is: CVE-2025-15682 is a high-severity denial of service vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation), published on 10 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-2025-15682 in the wild and no public exploit code.

Affected product: TBEA TLogger (TBEA Communication Box 3rd Generation). 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-2025-15682/ (Markdown: https://insights.sbomify.com/CVE-2025-15682/index.md)
```

## Sources

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

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