Vulnerability in crun (UBUNTU-CVE-2026-47766)

Summary

Vulnerability in crun (UBUNTU-CVE-2026-47766). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called UBUNTU-CVE-2026-47766 was discovered in crun.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "crun UBUNTU-CVE-2026-47766".

UBUNTU-CVE-2026-47766 (crun). Severity: Info.
Response plan:

Check the vendor advisory for affected versions and the patched release.
If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.

❓ What is the problem

A weakness (UBUNTU-CVE-2026-47766) in crun. A serious software flaw has been identified.

📍 Affected scope

Target versions of crun (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Info. Low severity or not yet rated.

🔧 How to fix

Update to the patched release as listed in the vendor advisory.

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.