# CVE-2025-24919: Dell ControlVault3/ControlVault3 Plus deserialization of untrusted input vulnerability

> A deserialization flaw in Dell ControlVault firmware allows arbitrary code execution if an attacker compromises the firmware to send malicious responses.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-fvxq-m6wq-rqqv

## What is CVE-2025-24919?

CVE-2025-24919 is a high-severity unsafe deserialization vulnerability in Broadcom BCM5820X, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A deserialization of untrusted input vulnerability exists in the cvhDecapsulateCmd functionality of Dell ControlVault3 prior to 5.15.10.14 and ControlVault3 Plus prior to 6.2.26.36. A specially crafted ControlVault response to a command can lead to arbitrary code execution. An attacker can compromise a ControlVault firmware and have it craft a malicious response to trigger this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-24919 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24919 is a high-severity unsafe deserialization vulnerability in Broadcom BCM5820X, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24919 in the wild and no public exploit code.

Affected product: Broadcom BCM5820X. 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-24919/ (Markdown: https://insights.sbomify.com/CVE-2025-24919/index.md)
```

## Sources

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

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