CVE-2026-133553: crun · CWE-367
Source GCVE Database
Not known to be exploited · CVSS 7.8 High.
Data as of 20 Nov 2026, 07:36 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 7.8 |
|---|
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10crun | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8container-tools:rhel8/crun | Affected– | Fixed in– |
| Red Hat Enterprise Linux 9crun | Affected– | Fixed in– |
| Red Hat Hardened Imagescrun | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4crun | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8 | Affected– | Fixed in– |
AI-suggested
Red Hat advises not to grant untrusted containers writable volumes that are also the destination of a tmpcopyup tmpfs mount. This includes avoiding Podman configurations with --read-only when the image symlinks /var/tmp into the volume and avoiding --tmpfs mounts pointed into shared volumes.
Description
A vulnerability in crun allows a container sharing a writable volume with another container to exploit a race condition when copying files onto a tmpfs mounted with tmpcopyup. The flaw arises because crun opens the destination path twice, enabling the attacker to change the path between lookups and cause image files to be copied onto host files, including sensitive files under /proc/sys. This can lead to high impact on confidentiality, integrity, and availability.