# CVE-2025-55423: Command injection in n/a

> Attackers can execute arbitrary OS commands on ipTIME routers via unsanitized input in the upnp_relay function.

- **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:** 20 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-495m-v35r-f849

## What is CVE-2025-55423?

CVE-2025-55423 is a critical command injection vulnerability in n/a, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability exists in the upnp_relay() function in multiple ipTIME router models because the controlURL value used to pass port-forwarding information to an upper router is passed to system() without proper validation or sanitization, allowing OS command injection.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 163 products.


Products: Iptime A1004 Firmware, Iptime A1004ns Firmware, Iptime A1004v Firmware, Iptime A104 Firmware, Iptime A104ns Firmware, Iptime A104r Firmware, Iptime A1 Firmware, Iptime A2003mu Firmware, Iptime A2003ns-Mu Firmware, Iptime A2004 Firmware, Iptime A2004mu Firmware, Iptime A2004ns-Mu Firmware, Iptime A2004ns-R Firmware, Iptime A2004ns Firmware, Iptime A2004nsplus Firmware, Iptime A2004plus Firmware, Iptime A2004r Firmware, Iptime A2004se Firmware, Iptime A2008 Firmware, Iptime A3002mesh Firmware and 143 more.

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

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

## Is CVE-2025-55423 being exploited?

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

Public exploit code:

- https://github.com/logis11/CVE-2025-55423-analysis-and-reproduction (github_poc): https://github.com/logis11/CVE-2025-55423-analysis-and-reproduction

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55423 is a critical command injection vulnerability in n/a, published on 20 Jan 2026. 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-55423 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-55423/ (Markdown: https://insights.sbomify.com/CVE-2025-55423/index.md)
```

## Sources

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

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