{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24054 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-24054 is a high-severity vulnerability in kata-containers, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24054 and fix it if it is affected.\n\nWhat it is: CVE-2026-24054 is a high-severity vulnerability in kata-containers, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24054 exists.\n\nAffected product: kata-containers. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24054/ (Markdown: https://insights.sbomify.com/CVE-2026-24054/index.md)","id":"CVE-2026-24054","markdown":"https://insights.sbomify.com/CVE-2026-24054/index.md","name":"CVE-2026-24054","record":{"aliases":["AZL-75770","GHSA-5fc8-gg7w-3g5c","OESA-2026-1377","OESA-2026-1433","OESA-2026-1434","OESA-2026-1435","OESA-2026-1436","OESA-2026-1437","OESA-2026-1599"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kata Containers runtime","requires_auth":"none","summary":"A malformed container image can cause the host block device to be hotplugged into the VM, leading to host filesystem errors and potential data corruption.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kata_containers","vendor":"katacontainers"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:P","version":"4.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. In versions prior to 3.26.0, when a container image is malformed or contains no layers, containerd falls back to bind-mounting an empty snapshotter directory for the container rootfs. When the Kata runtime attempts to mount the container rootfs, the bind mount causes the rootfs to be detected as a block device, leading to the underlying device being hotplugged to the guest. This can cause filesystem-level errors on the host due to double inode allocation, and may lead to the host's block device being mounted as read-only. Version 3.26.0 contains a patch for the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Other in kata-containers","id":"CVE-2026-24054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Langfuse Slack OAuth Installation Endpoint Lacks Authentication, Enabling Arbitrary Project Linking","id":"CVE-2026-24055"},"packages":[],"prev":{"headline":"Cluade Code has a Path Restriction Bypass via ZSH Clobber which Allows Arbitrary File Writes","id":"CVE-2026-24053"},"products":["kata-containers"],"published":"2026-01-29","related":[{"cvss_score":9.4,"headline":"Kata Container to Guest micro VM privilege escalation","id":"CVE-2026-24834","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2020-27151","kev_date_added":null,"published":"2020-12-07"},{"cvss_score":5.8,"headline":"Kata Containers have VM Escape via virtiofsd Argument Injection through Default-Enabled Pod Annotations","id":"CVE-2026-44210","kev_date_added":null,"published":"2026-07-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-29","vendors":["kata-containers"]},"summary":"A malformed container image can cause the host block device to be hotplugged into the VM, leading to host filesystem errors and potential data corruption.","url":"https://insights.sbomify.com/CVE-2026-24054/"}