# CVE-2025-15680: Information Disclosure via UART

> A physically proximate attacker can connect to the UART interface to view debug logs, revealing sensitive system and network configuration details.

- **Severity:** Low 2.4 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-f723-8mf9-84xv

## What is CVE-2025-15680?

CVE-2025-15680 is a low-severity vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation), published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TBEA TLogger V2.1.0.0B0.0.0.0 exposes a UART interface on the device's circuit board without sufficient protection. A physically proximate attacker can connect to the UART interface and observe the device boot process and runtime debug output. The disclosed information includes operating system details, software versions, network configuration, filesystem paths, and other implementation and debugging information that may assist an attacker in further compromising the device.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-15680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15680 is a low-severity vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation), published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15680 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-15680/ (Markdown: https://insights.sbomify.com/CVE-2025-15680/index.md)
```

## Sources

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

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