# CVE-2025-41426: Vertiv Liebert RDU101 and UNITY Stack-based Buffer Overflow

> An attacker can exploit a stack-based buffer overflow in Vertiv Liebert RDU101 and UNITY devices to execute arbitrary code.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** GHSA-h5xv-74x6-xp2m

## What is CVE-2025-41426?

CVE-2025-41426 is a critical memory corruption vulnerability in Vertiv Liebert IS-UNITY, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected Vertiv products contain a stack based buffer overflow vulnerability. An attacker could exploit this vulnerability to gain code execution on the device.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2025-41426 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41426 is a critical memory corruption vulnerability in Vertiv Liebert IS-UNITY, published on 21 May 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-41426 in the wild and no public exploit code.

Affected product: Vertiv Liebert IS-UNITY. 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-41426/ (Markdown: https://insights.sbomify.com/CVE-2025-41426/index.md)
```

## Sources

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

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