Skip to main content
VulnerabilityPublished

CVE-2026-133553: Red Hat Hardened Images · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects Red Hat Hardened ImagesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 20 Nov 2026, 04:06 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.8
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Red Hat Hardened ImagescrunAffected–Fixed in–

AI-suggested

Red Hat advises not to give untrusted containers writable volumes that are also the destination of a tmpcopyup tmpfs. This includes avoiding Podman configurations with --read-only when the image symlinks /var/tmp into the volume and avoiding --tmpfs mounts pointed into the shared volume. Monitor the Red Hat advisory for updates on patch availability.

Description

CVE-2026-133553 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in crun used by Red Hat Hardened Images. The flaw occurs when crun copies files onto a tmpfs mounted with tmpcopyup and opens the destination path a second time by name. A container sharing a writable volume with the container being created can exploit this to change the path between lookups, causing crun to copy image files onto host files, including sensitive files under /proc/sys. This can lead to unauthorized modification of host files and potential privilege escalation.

References

Community reviews

Loading reviews…