LXD: SSRF via image import from URL allows internal network probing by authenticated users

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-28385: 0.28% estimated exploitation activity in the next 30 days; percentile 20.38 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The LXD image import-from-URL endpoint (`POST /1.0/images` with `source.type=url`) makes server-side HTTP requests to an attacker-supplied URL without any private-IP or loopback blocking. An authenticated user with the `can_create_images` entitlement can force the LXD daemon to connect to internal network addresses (127.0.0.1, RFC1918 ranges, cloud metadata endpoints), enabling port scanning via error-based inference and interaction with internal HTTP services from the daemon's privileged network position.

Severity - Attack Vector: Network — LXD API is network-accessible. - Attack Complexity: Low — Single crafted API request with no special conditions. - Privileges Required: Low — Requires `can_create_images` entitlement, a non-admin permission commonly delegated to regular users. - User Interaction: None. - Scope: Changed — The attacker leverages LXD's privileged network position to probe and interact with internal services that are outside the…

Published by the source

6 Nov 2026, 18:29 UTC

Last modified by the source

6 Nov 2026, 18:45 UTC

Source last checked

7 Nov 2026, 06:05 UTC

1. Revision 2 · amended · 7 Nov 2026

   Amended from osv record GHSA-3gq2-x4qg-p4g6

2. Revision 1 · created · 6 Nov 2026

   Published from ghsa record GHSA-3gq2-x4qg-p4g6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28385

Advisory: LXD: SSRF via image import from URL allows internal network probing by authenticated users
IDs: CVE-2026-28385, GHSA-3gq2-x4qg-p4g6
Record: https://patchnext.com/advisories/cve-2026-28385 (revision 2, source checked 7 Nov 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/canonical/lxd 0.0.0-20261005133302-c4a919f3f4e2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/canonical/lxd: affected < 0.0.0-20261005133302-c4a919f3f4e2; fixed in 0.0.0-20261005133302-c4a919f3f4e2

## Suggested inspection (read-only)
- Go github.com/canonical/lxd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/canonical/lxd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3gq2-x4qg-p4g6 (GitHub-reviewed advisory GHSA-3gq2-x4qg-p4g6 lists affected ranges: Go github.com/canonical/lxd >=0 <0.0.0-20261005133302-c4a919f3f4e2)
- Verified: https://osv.dev/vulnerability/GHSA-3gq2-x4qg-p4g6 (OSV record GHSA-3gq2-x4qg-p4g6 lists affected ranges: Go github.com/canonical/lxd >=0 <0.0.0-20261005133302-c4a919f3f4e2 (fixed))

Commands are suggestions: review each one before running it.