Advisory record · GHSA-67wx-r9xr-x75x

Incus has Unbounded YAML Metadata Decode via Parsing

CVSS 5.3 MediumEPSS 0.0027 · 19th percentile

Published by the GitHub Advisory Database at 4 May 2026, 19:44 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/lxc/incus/v6/cmd/incusdGo<=6.23.0No fixed version yet
Identifiers
GHSA-67wx-r9xr-x75x · CVE-2026-41648 · GO-2026-5168
Weakness (CWE)
CWE-770
Published
4 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Incus (github.com/lxc/incus/v6/cmd/incusd) versions up to and including 6.23.0 are affected. An authenticated user with permission to upload an image or backup archive can supply a crafted tarball whose YAML metadata file is very large, causing the server to allocate a large amount of memory while parsing it, which could exhaust memory or degrade the service. No fixed version is listed in the advisory; the source points to a patch in release v7.0.0, which should be checked before relying on it.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0027, the 19th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.