cve.bz

CVE-2026-28385 canonical lxd: SSRF

5.0 mediumExploit referenceEPSS 0.3%Fix available

Medium (5.0) in canonical lxd. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/canonical/lxd 0.0.0-20261005133302-c4a919f3f4e2.

On this page
In Canonical LXD versions 4.12 through 6.9, a Server-Side Request Forgery (SSRF) vulnerability in the image import functionality allows authenticated users with the can_create_images entitlement to interact with internal network infrastructure via the /images endpoint. When importing an image from a URL source, the LXD daemon fails to validate or restrict outbound destination IP addresses, allowing connections to loopback, RFC1918 private ranges, and cloud metadata endpoints. This enables error-based port scanning and unauthorized interaction with internal HTTP services from the daemon's network position.

Severity

CVSS 3.1

5.0 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-26. 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-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-28385 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-28385?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-28385?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-28385 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
Canonical lxdfrom 6.0 before 6.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3gq2-x4qg-p4g6Gogithub.com/canonical/lxd<0.0.0-20261005133302-c4a919f3f4e20.0.0-20261005133302-c4a919f3f4e2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13lxdno fix listedDEBIAN-CVE-2026-28385

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery 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