# CVE-2025-58354: Kata Containers coco-tdx malicious host can circumvent initdata verification

> A malicious host can bypass initdata verification in Kata Containers on TDX systems, allowing arbitrary workload execution while passing attestation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/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:** 23 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-989w-4xr2-ww9m

## What is CVE-2025-58354?

CVE-2025-58354 is a medium-severity vulnerability in kata-containers, published on 23 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. In Kata Containers versions from 3.20.0 and before, a malicious host can circumvent initdata verification. On TDX systems running confidential guests, a malicious host can selectively fail IO operations to skip initdata verification. This allows an attacker to launch arbitrary workloads while being able to attest successfully to Trustee impersonating any benign workload. This issue has been patched in Kata Containers version 3.21.0.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2025-58354 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58354 is a medium-severity vulnerability in kata-containers, published on 23 Sep 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-58354 in the wild and no public exploit code.

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

## Sources

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

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