# CVE-2025-26410: Weak Hard-coded Credentials

> Attackers can use hard-coded credentials to log into Wattsense Bridge devices via serial interface, gaining unauthorized access and control.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-jj4x-g447-hm4m

## What is CVE-2025-26410?

CVE-2025-26410 is a critical vulnerability in Wattsense Bridge, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The firmware of all Wattsense Bridge devices contain the same hard-coded user and root credentials. The user password can be easily recovered via password cracking attempts. The recovered credentials can be used to log into the device via the login shell that is exposed by the serial interface. The backdoor user has been removed in firmware BSP >= 6.4.1.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-26410 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26410 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26410 is a critical vulnerability in Wattsense Bridge, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26410 exists.

Affected product: Wattsense Bridge. 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-26410/ (Markdown: https://insights.sbomify.com/CVE-2025-26410/index.md)
```

## Sources

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

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