Loading story…
Canonical LXD disclosed and patched multiple flaws that let authenticated users bypass project-level restrictions during cross-project moves, copies, clustered migrations, and restore operations. The most severe issues, tracked as CVE-2026-63300 and CVE-2026-62420, carry CVSS 9.9 ratings and allow attackers with instance-creation rights in a restricted project to introduce disallowed instance configurations by first creating them in an unrestricted project or by abusing clustered migration flows that were treated as internal notifications. The bypasses could defeat controls such as restricted.containers.lowlevel, restricted.devices.*, and restricted.networks.access, potentially enabling host command execution or other high-impact policy violations.
A related flaw, CVE-2026-63299, lets authenticated users evade project disk and volume limits during cross-project storage volume moves and snapshot restores, with a CVSS 8.5 score. Canonical addressed the issues in LXD pull requests #18605 and #18651, adding validation of target-project restrictions for instance moves and copies, enforcing snapshot restrictions during backup restore, and hardening checks in the stable 5.21 branch. Organizations using LXD, especially clustered deployments and restricted multi-tenant projects, should upgrade to the latest patched release and review project restriction and migration controls.
Get the actors, campaigns, and ATT&CK mapping behind it.
7 events from the most recent confirmed update back to the earliest known activity.
A CVE record was published for a high-severity LXD authorization bypass affecting cross-project volume moves and volume snapshot restores, allowing authenticated users to evade project-level disk and volume limits.
A CVE record was published for a critical LXD authorization bypass in clustered cross-project migrations where a destination node treats the request as an internal cluster notification and skips project restriction checks.
A CVE record was published for a critical LXD improper validation flaw in instancePostMigration that lets an authenticated attacker bypass restricted-project controls by moving an instance from an unrestricted project into a restricted one, potentially enabling host command execution.
Kadin Sayani force-pushed the stable-5.21 backport pull request #18651 and marked it ready for review, carrying the same hardening changes to enforce target-project restrictions during cross-project operations and backup restore.
Canonical opened and marked ready for review a security hardening pull request on the main branch that added target-project restriction checks for cross-project instance moves, copies, and backup restores as further hardening for GHSA-47w9-6r3f-938g.
Tomponline merged pull request #18651 into canonical:stable-5.21 with 34 checks passing. The backport included additional enforcement for cross-project instance moves, cross-project copies, and snapshot restrictions during backup restore.
Tomponline merged pull request #18605 into canonical:main, bringing in checks that enforce project restrictions during cross-project instance moves and copies and during backup restores involving snapshots. The merged PR also included tests to prevent bypass of restricted project policies.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
5 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
The containerd project released patches for five vulnerabilities in its CRI and image-handling components, including three **critical** flaws tracked as `CVE-2026-50195`, `CVE-2026-53488`, and `CVE-2026-53492`, alongside `CVE-2026-53489` and `CVE-2026-47262`. According to the project’s disclosure and an AWS security bulletin, the bugs could let attackers poison a node’s local image cache with crafted checkpoint images, pass unvalidated image labels that may lead to arbitrary host command execution through label-consuming plugins, and abuse untrusted CDI annotations during checkpoint restore to bypass Kubernetes device allocation controls. The remaining issues include a **high-severity** arbitrary host file-read path through `kubectl logs` by restoring a symlinked `container.log` from a checkpoint image, and a **moderate** denial-of-service flaw that can exhaust memory and crash the `containerd` process. Fixes are available in containerd `2.3.2`, `2.2.5`, and `2.1.9` for all five vulnerabilities, while versions `2.0.10` and `1.7.33` address `CVE-2026-53488` and `CVE-2026-47262`; maintainers urged immediate upgrades and said containers restored from untrusted checkpoints may need to be recreated to remove smuggled CDI configuration tied to `CVE-2026-53492`.
Jul 1, 2026
Ubuntu disclosed mitigation guidance for **CVE-2026-53359** ("**Januscape**"), a Linux kernel local privilege escalation flaw affecting nested virtualization in **KVM** on Intel and AMD `x86_64` systems. The issue impacts Ubuntu releases from **14.04 through 26.04**, and a public proof-of-concept shows that a guest can crash the hypervisor host; Ubuntu warned that, in cloud environments with nested virtualization enabled, exploitation could potentially compromise the host or other tenants. The advisory said the required fix must be applied to the **hypervisor kernel**, while **unprivileged containers are not affected**; however, privileged containers and systems exposing `/dev/kvm` to non-privileged users may face elevated risk. Canonical's Ubuntu CVE tracker lists **CVE-2026-53359** among several high-priority Linux kernel vulnerabilities marked as affecting Ubuntu package families including `linux`, `linux-hwe`, `linux-hwe-5.4`, `linux-hwe-5.8`, and `linux-hwe-5.11`, with fixes noted as resolved upstream in the Linux kernel. Separate Linux security update notices also highlighted active kernel patching activity for other serious flaws, including **CVE-2026-46331**, a `pedit` subsystem privilege-escalation bug with a disclosed proof-of-concept reported to exist in the wild, and **CVE-2026-52951**, a `drm/xe/dma-buf` use-after-free issue that can trigger denial of service; organizations were urged to test and deploy distributor patches from vendors such as Ubuntu and Red Hat.
Jul 14, 2026
Multiple vulnerabilities were discovered in the use of LUKS2 disk encryption within confidential computing systems, allowing attackers with write access to storage disks to extract or modify confidential data. These flaws stem from malleable metadata headers in LUKS2, which can be exploited to trick trusted execution environment (TEE) guests into encrypting data with a null cipher, effectively disabling encryption. The vulnerabilities impact several confidential computing frameworks, including Edgeless Constellation, and are tracked under CVE-2025-59054 and CVE-2025-58356. Affected projects have released patches, and users are advised to update to the latest versions and ensure remote attestation reports reject pre-patch versions. Specifically, the Constellation Confidential Kubernetes platform was found to allow insecure use of LUKS2-encrypted persistent storage partitions. Due to unsafe handling of null keyslot algorithms in cryptsetup versions prior to 2.8.1, Constellation's CVM image could treat unencrypted volumes as confidential, exposing sensitive data. The vulnerability is addressed in Constellation version 2.24.0 and cryptsetup 2.8.1. There is no evidence of exploitation in the wild, but organizations using these frameworks should apply mitigations immediately to prevent potential data compromise.
Jun 29, 2026