# CVE-2025-28236: Code injection in n/a

> Attackers can execute arbitrary code on Nautel VX transmitters by uploading a malicious firmware update package.

- **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:** 18 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-485p-gmh5-r688

## What is CVE-2025-28236?

CVE-2025-28236 is a critical code injection vulnerability in n/a, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nautel VX Series transmitters VX SW v6.4.0 and below was discovered to contain a remote code execution (RCE) vulnerability in the firmware update process. This vulnerability allows attackers to execute arbitrary code via supplying a crafted update package to the /#/software/upgrades endpoint.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

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

## Is CVE-2025-28236 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28236 is a critical code injection vulnerability in n/a, published on 18 Apr 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-28236 exists.

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-28236/ (Markdown: https://insights.sbomify.com/CVE-2025-28236/index.md)
```

## Sources

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

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