Link Following Affecting crun-krun package, versions <0:1.28-2.hum1


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

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-RHEL10-CRUNKRUN-21249817
  • published20 Oct 2026
  • disclosed14 Aug 2026

Introduced: 14 Aug 2026

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

How to fix?

Upgrade RHEL:10 crun-krun to version 0:1.28-2.hum1 or higher.
This issue was patched in RHSA-2026:54855.

NVD Description

Note: Versions mentioned in the description apply only to the upstream crun-krun package and not the crun-krun package as distributed by RHEL. See How to fix? for RHEL:10 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 -&gt; pts/ptmx symlink. Version 1.28 fixes the issue.

CVSS Base Scores

version 3.1