# CVE-2025-53963: Hardcoded credentials in n/a

> Attackers can gain root access via weak default credentials on unsupported Thermo Fisher Ion Torrent devices, leading to full system compromise.

- **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:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-mmhc-m89q-9v2j

## What is CVE-2025-53963?

CVE-2025-53963 is a critical vulnerability in n/a, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Thermo Fisher Ion Torrent OneTouch 2 INS1005527 devices. They run an SSH server accessible over the default port 22. The root account has a weak default password of ionadmin, and a password change policy for the root account is not enforced. Thus, an attacker with network connectivity can achieve root code execution. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Thermofisher Ion Torrent Onetouch 2 Firmware.

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

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

## Is CVE-2025-53963 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-54304](https://insights.sbomify.com/CVE-2025-54304/): Misconfiguration in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53963 is a critical vulnerability in n/a, published on 4 Dec 2025. 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-53963 in the wild and no public exploit code.

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

## Sources

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

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