# CVE-2026-41648: GO-2026-5168 - Incus has Unbounded YAML Metadata Decode via Parsing in github.com/lxc/incus

Source: https://junglewise.ai/threats/cve-2026-41648-incus-has-unbounded-yaml-metadata-decode-via-parsing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-07  
License: CC BY 4.0 with a link back

CVE-2026-41648 · Severity: medium · CVSS 5 · Published 2026-05-07

Incus is a system container and virtual machine manager. Prior to version 7.0.0, user provided image and backup tarballs would be unpacked and YAML files parsed without any size restrictions. This was making it easy for an authenticated user to provide a crafted image or backup tarball that when parsed by Incus would lead to a very large YAML document being loaded into memory, potentially causing the entire server to run out of memory. This issue has been patched in version 7.0.0.

Technologies: [github.com/lxc/incus (Go)](https://junglewise.ai/threats/technologies/github-com-lxc-incus), [github.com/lxc/incus/v6 (Go)](https://junglewise.ai/threats/technologies/github-com-lxc-incus-v6), [github.com/lxc/incus/v6/cmd/incusd (Go)](https://junglewise.ai/threats/technologies/github-com-lxc-incus-v6-cmd-incusd), [Linuxcontainers Incus](https://junglewise.ai/threats/technologies/linuxcontainers-incus). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Linuxcontainers](https://junglewise.ai/threats/vendors/linuxcontainers).

## Quick answers

**Is CVE-2026-41648 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-41648 being exploited in the wild.

**How severe is CVE-2026-41648?** Medium severity, with a CVSS score of 5, published 7 May 2026.

**Which products and versions are affected?** github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v6/cmd/incusd (Go) SEMVER:introduced=0,last_affected=6.23.0.

**Is there a fix for CVE-2026-41648?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-41648?** Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v6/cmd/incusd (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- github.com/lxc/incus (Go) SEMVER:introduced=0
- github.com/lxc/incus/v6 (Go) SEMVER:introduced=0
- github.com/lxc/incus/v6/cmd/incusd (Go) SEMVER:introduced=0,last_affected=6.23.0
- Linuxcontainers Incus

## Identifiers

- CVE-2026-41648
- GHSA-67wx-r9xr-x75x
- GO-2026-5168

## Related threats

- [Incus project restriction bypass in instance copy](https://junglewise.ai/threats/cve-2026-55622-incus-project-restriction-bypass-in-instance-copy)
- [Incus authorization bypass in custom volume copy](https://junglewise.ai/threats/cve-2026-55621-incus-authorization-bypass-in-custom-volume-copy)
- [LXC Incus arbitrary file write via image hash path traversal](https://junglewise.ai/threats/cve-2026-48769-lxc-incus-arbitrary-file-write-via-image-hash-path-traversal)
- [LXC Incus nil-pointer dereference in CreateCustomVolumeFromBackup](https://junglewise.ai/threats/cve-2026-48756-lxc-incus-nil-pointer-dereference-in-createcustomvolumefrombackup)
- [LXC Incus argument injection in backup compression algorithm](https://junglewise.ai/threats/cve-2026-48755-lxc-incus-argument-injection-in-backup-compression-algorithm)