External risk intelligence

Incus S3 Path Traversal Allows Arbitrary File Creation and Command Execution

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-48753

Incus serves as a system container and virtual machine manager. The vulnerability exists within an S3 protocol upload endpoint. Such endpoints in container and storage management tools are commonly exposed as network-accessible services to facilitate remote file management, data synchronization, or integration with external cloud-native workflows.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability identified in Incus, a system container and virtual machine manager, impacting versions prior to 7.1.0. The issue resides in the S3 protocol upload endpoint, where a path traversal flaw could allow unauthorized creation of arbitrary files on the host system, potentially leading to command execution. The main concern is confirming relevance and exposure, as the vulnerability resides in a component that manages system containers and virtual machines.

  • Path traversal flaw in file uploads.
  • Critical vulnerability could lead to command execution.
  • Confirm relevance and assess exposure to Incus.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted requests to the S3 protocol upload endpoint of Incus. This endpoint, if exposed to the network, allows users with limited privileges to upload files. By manipulating the file path within these upload requests, an attacker can cause Incus to create arbitrary files on the host system. If these created files can be controlled by the attacker and subsequently executed, it could lead to the execution of commands on the host.

  • Requires limited privileges and network access.
  • Path traversal in S3 upload endpoint.
  • Arbitrary file creation and command execution.

Live Threat

Current exploitation, exposure, and threat context

The S3 protocol upload endpoint in Incus, when running a version prior to 7.1.0, is susceptible to path traversal. This flaw could enable an authenticated attacker to create arbitrary files on the host system, potentially leading to the execution of commands with the privileges of the Incus service.

  • Arbitrary file creation on the host.
  • Remote authenticated upload through S3 endpoint.
  • Host command execution possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Incus system container and virtual machine manager has a critical vulnerability in its S3 upload endpoint that could allow arbitrary file creation on the host and command execution. Teams responsible for managing infrastructure, virtualization, or container platforms should prioritize identifying all Incus deployments, assessing their exposure and business criticality, and confirming the accountable owner for remediation. Planning should then focus on risk-based actions, which may include coordinating with vendors, planning maintenance windows, or implementing temporary risk reduction measures.

  • Infrastructure and Platform Teams own the issue.
  • Verify Incus deployment and S3 endpoint reachability.
  • Plan remediation based on asset criticality and risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Incus and how is it used?

Incus is an open-source tool used for managing system containers and virtual machines. It allows users to run and orchestrate isolated operating systems or applications on a host machine, similar to other virtualization technologies that simplify infrastructure management.

What does CVE-2026-48753 mean for system security?

This vulnerability is classified as CWE-73, or External Control of File Name or Path. It means the software does not properly validate file paths during S3 protocol uploads, potentially allowing an attacker to write files to unintended locations on the host system.

How can an attacker trigger this vulnerability?

An attacker needs network access to the Incus S3 upload endpoint and limited user privileges. The bug is triggered by sending a specially crafted request that manipulates the file path. Note that simply having the service running is not enough; the attacker must be able to successfully authenticate and interact with that specific upload endpoint.

Do I need to worry if my Incus instance is internal?

Halo Surface Signal indicates that S3 endpoints in tools like Incus are often network-accessible to support remote workflows. While the risk is higher for internet-facing systems, you should evaluate if your internal network architecture sufficiently isolates the Incus service from untrusted users who might hold the necessary limited privileges to trigger this flaw.

When should I update my Incus software?

You should prioritize updating to version 7.1.0 immediately. Your first step is to inventory all running Incus deployments to identify which are using versions prior to 7.1.0, then assess their accessibility and plan for a maintenance window to apply the fix.

References