Directory Traversal Affecting libvirt package, versions <5.5.0-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.55% (42nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALPINE324-LIBVIRT-17301403
  • published11 Jun 2026
  • disclosed2 Aug 2019

Introduced: 2 Aug 2019

CVE-2019-10168  (opens in a new tab)
CWE-22  (opens in a new tab)
CWE-284  (opens in a new tab)
CWE-250  (opens in a new tab)

How to fix?

Upgrade Alpine:3.24 libvirt to version 5.5.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libvirt package and not the libvirt package as distributed by Alpine. See How to fix? for Alpine:3.24 relevant fixed versions and status.

The virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs, 4.x.x before 4.10.1 and 5.x.x before 5.4.1, accept an "emulator" argument to specify the program providing emulation for a domain. Since v1.2.19, libvirt will execute that program to probe the domain's capabilities. Read-only clients could specify an arbitrary path for this argument, causing libvirtd to execute a crafted executable with its own privileges.

CVSS Base Scores

version 3.1