Security readout for executives and security teams
Plain-English summary
Kata Containers before 3.27.0 can let someone inside a container alter the guest micro VM filesystem and gain root code execution inside that VM. The sources say current understanding does not show host or neighboring VM compromise, but the severity is still critical for Kata-backed workloads.
Executive priority
Treat this as urgent for platforms using Kata Containers, because a container-level user may gain root control inside the guest VM. It is not currently evidenced as a host escape, but affected shared infrastructure should be upgraded quickly to preserve tenant and workload isolation.
Technical view
The issue affects kata-containers versions before 3.27.0, with the advisory describing a Cloud Hypervisor-related path where a container user can modify the Guest micro VM filesystem. The assigned weaknesses are improper permission preservation and permission assignment. CVSS 3.1 is 9.4 with local attack vector, low complexity, no privileges, no user interaction, and changed scope.
Likely exposure
Exposure is most likely where Kata Containers earlier than 3.27.0 are deployed, particularly with Cloud Hypervisor-backed workloads. The bundle names kata-containers as the affected product. The advisory also notes an arm64 QEMU read-only NVDIMM limitation that may affect image-write boundaries until upstream support exists.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitation appears to require code execution as a container user in a vulnerable Kata workload. The described impact is root code execution inside the Guest micro VM, with host and other VM/container impact not currently established by the cited sources.
Researcher notes
Do not assume host compromise from the provided evidence. Focus triage on vulnerable Kata versions, Cloud Hypervisor usage, and the advisory's arm64 QEMU caveat. Patch linkage is clear through the 3.27.0 release and referenced commit, but exploit-in-the-wild evidence is not provided.
Mitigation direction
- Upgrade Kata Containers to version 3.27.0 or later.
- Prioritize Cloud Hypervisor-backed Kata deployments below 3.27.0.
- Review vendor guidance for platform-specific advisories and packaging status.
- Assess arm64 QEMU deployments against the advisory's NVDIMM read-only caveat.
- Restrict untrusted workload placement on vulnerable Kata nodes until remediated.
Validation and detection
- Inventory Kata Containers versions across clusters and hosts.
- Identify workloads using Kata runtime with Cloud Hypervisor.
- Confirm upgraded nodes report Kata Containers 3.27.0 or later.
- Review Red Hat advisory status if using Red Hat packaged components.
- Document any arm64 QEMU exposure for separate vendor tracking.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-281: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-732: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24834 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.56GitHub_MCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.56redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-19T17:03:55.479Z: Reported to Red Hat.
- 2026-02-19T15:57:50.691Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/kata-containers/kata-containers/security/advisories/GHSA-wwj6-vghv-5p64CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/kata-containers/kata-containers/commit/6a672503973bf7c687053e459bfff8a9652e16bfCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/kata-containers/kata-containers/releases/tag/3.27.0CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-24834CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2441025CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24834.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Preservation of Permissions
Improper Preservation of Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.