# CVE-2025-14097: Remote Code Execution Vulnerability in Radiometer Products

> Attackers can achieve remote code execution and unauthorized device management on Radiometer analyzers if the remote support feature is enabled.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-rjfq-mp68-v4f7

## What is CVE-2025-14097?

CVE-2025-14097 is a high-severity authentication bypass vulnerability in Radiometer Medical Aps ABL800 BASIC and ABL800 FLEX Analyzers, published on 17 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the application software of multiple Radiometer products may allow remote code execution and unauthorized device management when specific internal conditions are met. Exploitation requires that a remote connection is established with additional information obtained through other means.  The issue is caused by a weakness in the analyzer’s application software.                                                                                                                                                                                                Other related CVE's are CVE-2025-14095 & CVE-2025-14096.                                                                                                      Affected customers have been informed about this vulnerability. This CVE is being published to provide transparency.

Required Configuration for Exposure: Affected application software version is in use and remote support feature is enabled in the analyzer.                                                                                                                                                                        Temporary work Around: If the network is not considered secure, please remove the analyzer from the network.                         Permanent solution:
Customers should ensure the following:
•  The network is secure, and access follows best practices.
Local Radiometer representatives will contact all affected customers to discuss a permanent solution.                                                     
Exploit Status:

Researchers have provided working proof-of-concept (PoC). Radiometer is not aware of any publicly available exploits at the time of this publication.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-14097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14097 is a high-severity authentication bypass vulnerability in Radiometer Medical Aps ABL800 BASIC and ABL800 FLEX Analyzers, published on 17 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14097 in the wild and no public exploit code.

Affected product: Radiometer Medical Aps ABL800 BASIC and ABL800 FLEX Analyzers. 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-14097/ (Markdown: https://insights.sbomify.com/CVE-2025-14097/index.md)
```

## Sources

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

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