GHSA-ccjc-4qc3-jxqc: Incus has an arbitrary file write via path traversal in S3 multipart upload
Incus before version 7.1.0 contains a vulnerability in its S3 protocol upload endpoint that allows path traversal via an unsanitized upload ID. This flaw enables an attacker with limited privileges to write arbitrary files on the host system, potentially leading to arbitrary command execution. The vulnerability arises because the upload ID is appended directly to the uploads directory path without proper validation. A proof-of-concept demonstrates exploitation by writing to sensitive system files such as /etc/cron.d, enabling persistent command execution. This vulnerability is classified as critical due to its potential impact on confidentiality, integrity, and availability.
AI Analysis
Technical Summary
The Incus S3 multipart upload implementation in internal/server/storage/s3/local/multipart.go improperly handles user-controlled upload IDs by appending them unsanitized to the uploads directory path. This path traversal vulnerability allows attackers to create or overwrite arbitrary files on the host filesystem. Exploitation can lead to arbitrary command execution by writing malicious cron jobs or other scripts. The vulnerability affects versions prior to 7.1.0. No official patch links are provided in the data, and the vendor has not confirmed a fix in the provided information.
Potential Impact
Successful exploitation results in arbitrary file write on the host system, which can be leveraged to execute arbitrary commands with the privileges of the Incus process. This compromises system confidentiality, integrity, and availability, potentially allowing persistent remote code execution.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the S3 upload endpoint to trusted users only and monitor for suspicious activity related to multipart uploads. Avoid exposing the S3 API publicly or to untrusted networks.
GHSA-ccjc-4qc3-jxqc: Incus has an arbitrary file write via path traversal in S3 multipart upload
Description
Incus before version 7.1.0 contains a vulnerability in its S3 protocol upload endpoint that allows path traversal via an unsanitized upload ID. This flaw enables an attacker with limited privileges to write arbitrary files on the host system, potentially leading to arbitrary command execution. The vulnerability arises because the upload ID is appended directly to the uploads directory path without proper validation. A proof-of-concept demonstrates exploitation by writing to sensitive system files such as /etc/cron.d, enabling persistent command execution. This vulnerability is classified as critical due to its potential impact on confidentiality, integrity, and availability.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Incus S3 multipart upload implementation in internal/server/storage/s3/local/multipart.go improperly handles user-controlled upload IDs by appending them unsanitized to the uploads directory path. This path traversal vulnerability allows attackers to create or overwrite arbitrary files on the host filesystem. Exploitation can lead to arbitrary command execution by writing malicious cron jobs or other scripts. The vulnerability affects versions prior to 7.1.0. No official patch links are provided in the data, and the vendor has not confirmed a fix in the provided information.
Potential Impact
Successful exploitation results in arbitrary file write on the host system, which can be leveraged to execute arbitrary commands with the privileges of the Incus process. This compromises system confidentiality, integrity, and availability, potentially allowing persistent remote code execution.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the S3 upload endpoint to trusted users only and monitor for suspicious activity related to multipart uploads. Avoid exposing the S3 API publicly or to untrusted networks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-ccjc-4qc3-jxqc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-48753"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a3ef78d27e9c79719ff4974
Added to database: 06/26/2026, 22:05:01 UTC
Last enriched: 06/26/2026, 22:15:57 UTC
Last updated: 06/26/2026, 22:15:57 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.