# CVE-2025-2605: Authenticated command injection

> Authenticated attackers can execute arbitrary OS commands and escalate privileges in Honeywell MB-Secure systems.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2025
- **Updated:** 17 May 2025
- **Also known as:** GHSA-4p7f-6rw5-m5v7

## What is CVE-2025-2605?

CVE-2025-2605 is a critical command injection vulnerability in Honeywell MB-Secure, published on 2 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Honeywell MB-Secure allows Privilege Abuse. This issue affects MB-Secure: from V11.04 before V12.53 and MB-Secure PRO from V01.06 before V03.09.Honeywell also recommends updating to the most recent version of this product.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 2 products.


Products: Honeywell Mb-Secure Firmware, Honeywell Mb-Secure Pro Firmware.

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

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

## Is CVE-2025-2605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2605 is a critical command injection vulnerability in Honeywell MB-Secure, published on 2 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2605 in the wild and no public exploit code.

Affected product: Honeywell MB-Secure. 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-2605/ (Markdown: https://insights.sbomify.com/CVE-2025-2605/index.md)
```

## Sources

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

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