Severity by source
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionNVD
A flaw was found in assisted-migration-agent. An unauthenticated attacker, located on the same local area network (LAN), can exploit a path traversal vulnerability. By crafting a specially designed gzipped tarball, the attacker can bypass security checks and write arbitrary files to the system. This could ultimately lead to the execution of unauthorized code on the appliance.
AnalysisAI
Arbitrary file write in kubev2v assisted-migration-agent allows an unauthenticated attacker on the same LAN to achieve code execution on the appliance by uploading a crafted gzipped tarball that bypasses path traversal checks via chained symlinks. The flaw resides in the VDDK tarball extraction routine (extractTarGz in internal/services/vddk.go) and has a high CVSS of 9.6 due to scope change and full CIA impact, though no public exploit has been identified at time of analysis.
Technical ContextAI
The assisted-migration-agent is part of the kubev2v project, which facilitates VM migrations to Kubernetes/KubeVirt platforms. The vulnerable component handles upload and extraction of VMware Virtual Disk Development Kit (VDDK) tarballs (e.g., VMware-vix-disklib-8.0.3-*.tar.gz). The root cause is CWE-59 (Improper Link Resolution Before File Access, aka 'Link Following'): the original extractTarGz function validated tar entry paths individually but did not resolve symlinks in parent directories before writing subsequent entries. An attacker could include a symlink entry like 'a/x -> ..' followed by a regular file 'a/x/evil.sh', causing the second write to land outside the destination directory. The fix (PR #256) calls filepath.EvalSymlinks on the parent path before each write and rejects entries whose resolved parent escapes destDir or resolves to the root destination itself.
RemediationAI
Upstream fix available (PR/commit https://github.com/kubev2v/assisted-migration-agent/pull/256); a released patched version is not independently confirmed in the provided intelligence, so consumers should pull a build that includes the PR #256 changes to internal/services/vddk.go or track the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-53476 for an updated package. As a compensating control until patched code is deployed, restrict network access to the agent's upload endpoint using host-based firewall rules or network policies so only trusted migration controllers on a dedicated management VLAN can reach it - this directly neutralizes the AV:A LAN-adjacency requirement at the cost of requiring network reconfiguration. Operators who can tolerate a functional outage can also temporarily disable the VDDK upload feature, accepting that VMware-to-KubeVirt migrations dependent on VDDK will fail until the patch is applied. Monitor logs for tar extraction errors and unexpected file writes outside the configured destDir as a detection backstop.
More in Assisted Migration Agent
View allSame weakness CWE-59 – Improper Link Resolution Before File Access
View allSame technique Path Traversal
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36033
GHSA-7j4w-x8x8-5mvg