cve.bz

CVE-2026-48753 lxc incus: External Control of File Name or Path

9.9 criticalEPSS 0.7%Fix available

Critical (9.9) in lxc incus. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/lxc/incus/v7/cmd/incusd 7.1.0.

On this page
Incus is a system container and virtual machine manager. Prior to version 7.1.0, 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. Version 7.1.0 fixes the issue.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-73 External Control of File Name or Path
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-48753 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48753?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48753?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48753 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
lxc incus< 7.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-ccjc-4qc3-jxqcGogithub.com/lxc/incus/v7/cmd/incusd<7.1.07.1.0
GO-2026-5802Gogithub.com/lxc/incusall versionsno fix published
GO-2026-5802Gogithub.com/lxc/incus/v6all versionsno fix published
GO-2026-5802Gogithub.com/lxc/incus/v7<7.1.07.1.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14incus7.0.0-2DEBIAN-CVE-2026-48753
Ubuntu25.10, 26.10, Pro:24.04:LTS and 1 moreincusno fix listedUBUNTU-CVE-2026-48753
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedincus7.4-1.1openSUSE-SU-2026:11651-1
Alpinev3.24incus7.0.1-r0ALPINE-CVE-2026-48753

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

Incus is not shipped in any Red Hat product. The community Fedora package is affected.

Red Hat's mitigation

No mitigation is needed as Incus is not shipped in any Red Hat product.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-48753.

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON