/

CVE-2026-48753

Severity:

CRITICAL RISK

(9.9)

Path Traversal (CWE-73) in Incus S3 Upload Endpoint

CVE-2026-48753

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-73

Impact:

Arbitrary File Creation and Potential Command Execution

Severity:

CRITICAL RISK

(9.9)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical path traversal vulnerability in Incus allows an attacker to use the S3 protocol upload endpoint to create arbitrary files on the host.

Under conditions where the endpoint is reachable and accepts attacker-controlled paths, this may enable arbitrary command execution and host compromise.

Affected context

The vulnerability occurs in Incus deployments that expose or otherwise make the S3 protocol upload endpoint available to an attacker. It becomes risky when uploaded object names or destination paths are insufficiently constrained, allowing path information supplied through the request to escape the intended storage location and affect files on the host.

Exploit preconditions

  • Attack surface: Incus S3 protocol upload endpoint
  • Required access: Ability to reach and submit requests to the affected upload interface; authentication requirements depend on deployment configuration
  • Trigger point: Processing an upload whose supplied path is interpreted as a host filesystem destination
  • Why exploitation is possible: Insufficient path canonicalization and containment checks can allow writes outside the designated upload directory

Why this happens

The underlying bug is improper control of externally supplied file paths. When an application uses attacker-influenced object names or path components to construct filesystem destinations without canonicalization and strict directory-boundary validation, traversal sequences can redirect writes to unintended locations.

This behavior maps to CWE-73: External Control of File Name or Path, in which untrusted input influences filesystem operations. If a written file is later interpreted as executable code or configuration, the arbitrary write may be elevated into command execution.

Potential impact

  • An attacker may create or overwrite arbitrary files on the host
  • The affected service may be compromised through modified configuration or executable content
  • Arbitrary command execution may occur under the privileges of the Incus service
  • Host confidentiality, integrity, and availability could be affected
  • Compromised hosts may provide a path to further container or infrastructure compromise

General mitigation guidance

Mitigation generally focuses on treating upload names and paths as untrusted data and enforcing a strict storage boundary.

Common defensive patterns include:

  • Resolve and canonicalize candidate paths before writing files
  • Reject traversal components, absolute paths, and path interpretations that escape the intended directory
  • Generate server-side storage names instead of trusting client-provided filenames
  • Use a storage layer that does not expose direct host filesystem paths
  • Restrict the upload service to least-privilege filesystem and operating-system permissions
  • Isolate S3 upload processing from sensitive host directories and executable locations
  • Apply secure-by-default authentication, authorization, and endpoint exposure policies
  • Keep affected components maintained through the organization's normal security update process

How teams detect issues like this

Organizations can look for path traversal risks through:

  • Static analysis rules identifying filesystem writes whose paths derive from request or object-name data
  • Code review checks for missing canonicalization, containment validation, or rejection of absolute paths
  • Tests that verify uploads cannot escape an assigned storage directory
  • Runtime monitoring for unexpected file creation or modification outside approved upload locations
  • File-integrity monitoring for changes to service configuration, executable paths, and other sensitive host files
  • Policy enforcement restricting which interfaces can access upload endpoints and which service identities can write to disk

Automated security scanning and code-review tools may help identify path construction and arbitrary-file-write patterns.

Sources

SourceLink
github.comgithub.com/lxc/incus/security/advisories/GHSA-ccjc-4qc3-jxqc

Frequently asked

questions

It may be remotely exploitable when the affected S3 upload endpoint is reachable by an attacker and deployment controls do not sufficiently restrict access.

The required access depends on the Incus S3 endpoint's exposure and authentication configuration. The key prerequisite is the ability to submit an upload request that reaches the vulnerable path-handling logic.

Ensure that all upload destinations are server-controlled, canonicalized, and verified to remain within an approved storage directory. Avoid using client-controlled paths for direct host filesystem writes.

Apply strict path-boundary validation, use least-privilege service accounts, isolate upload storage, monitor sensitive file changes, and include traversal-focused tests and static analysis in development workflows.

Find out what's already
exploitable in your codebase.