Symlink Following Affecting crun package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.2% (9th 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-ECHOLATEST-CRUN-19683668
  • published11 Sept 2026
  • disclosed14 Aug 2026

Introduced: 14 Aug 2026

CVE-2026-47766  (opens in a new tab)
CWE-61  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest crun.

NVD Description

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

crun is an open source OCI Container Runtime fully written in C. Prior to version 1.28, crun's default device setup opens the container rootfs /dev directory without O_NOFOLLOW. If an OCI bundle contains rootfs/dev as a symlink and the bundle configuration does not mount /dev, crun follows that symlink and creates the default device nodes and stdio symlinks at the symlink target outside the container rootfs. In a local rootful crun replay, this created fixed device nodes and symlinks outside the rootfs before crun returned failure. A pre-existing file named ptmx in the target directory was also replaced by crun's forced ptmx -> pts/ptmx symlink. Version 1.28 fixes the issue.