LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2025: Kata Containers - Cloud Hypervisor guests persist filesystem changes to the underlying host image file

Kata Containers before 1.11.0 on Cloud Hypervisor persists guest filesystem changes to the underlying image file on the host. A malicious guest can overwrite the image file to gain control of all subsequent guest VMs. Since Kata Containers uses the same VM image file with all VMMs, this issue may also affect QEMU and Firecracker based guests.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

In affected Kata Containers deployments, a guest using Cloud Hypervisor could make filesystem changes that are saved into the host VM image. That can turn one compromised guest into a risk for later guests launched from the same image, creating cross-tenant or workload contamination risk.

Executive priority

Treat as high priority for container isolation platforms, especially multi-tenant or untrusted workload environments. The main business risk is one guest influencing future guests through a shared image, undermining isolation assumptions.

Technical view

CVE-2020-2025 is an improper access control issue in Kata Containers before 1.11.0. Guest filesystem writes on Cloud Hypervisor can persist to the underlying host image file. The CVE notes possible impact for QEMU and Firecracker guests because Kata uses the same VM image file across VMMs, but that is not confirmed here.

Likely exposure

Exposure is most likely in environments running Kata Containers before 1.11.0 with Cloud Hypervisor-backed guests and shared VM images. QEMU or Firecracker exposure is possible per the CVE wording, but the provided evidence does not prove specific affected configurations.

Exploitation context

The CVE describes a malicious guest overwriting the image file to affect subsequent guest VMs. CISA KEV status is false, and the provided sources do not cite active exploitation, public exploit availability, or observed attacks.

Researcher notes

The weakness is mapped to CWE-284 and has CVSS 8.8 with changed scope and high confidentiality, integrity, and availability impacts. Evidence is strongest for Cloud Hypervisor. The QEMU and Firecracker statement is conditional, so validate implementation behavior before broad classification.

Mitigation direction

  • Upgrade Kata Containers to 1.11.0 or later where applicable.
  • Review the linked upstream pull request and vendor guidance before production rollout.
  • Avoid sharing writable base VM images across untrusted guests.
  • Rebuild or replace any image that may have been exposed to untrusted guests.
  • Check whether QEMU or Firecracker deployments inherit the same image behavior.

Validation and detection

  • Inventory Kata Containers versions and VMM backends in use.
  • Identify deployments using Cloud Hypervisor with shared VM image files.
  • Confirm guest filesystem changes do not persist into host base images.
  • Review image integrity for images used after untrusted guest execution.
  • Document whether QEMU and Firecracker paths are affected in your environment.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-2025 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-2025Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Kata ContainersKata ContainersunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.