Skip to main content
Menu
CVEs

Red Hat race condition in crun lets attackers overwrite host files

CVE-2026-133553EUVD-2026-130833Published , updated

7.8HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

A local attacker with low privileges can make crun copy image files onto host files, including files under /proc/sys, in Red Hat Hardened Images. The attacker does this from a container that shares a writable volume with the container being created, changing the destination path between crun's two lookups.

Written by a model

Original description

A flaw was found in crun. When copying files onto a tmpfs mounted with tmpcopyup, crun opens the destination a second time by name. A container that shares a writable volume with the container being created can change that path between the two lookups, so crun copies image files onto host files, including files under /proc/sys.

Who should check

Teams running crun on RHEL 8, 9 or 10, OpenShift Container Platform 4 or 5, or Red Hat Hardened Images, where containers share writable volumes with other containers.

“Releases through 1.30.1 are affected”

bugzilla.redhat.com

What to do

  1. Check whether your setup matches what the bug needs.

    A tmpfs mount using tmpcopyup A second container sharing a writable volume with the container being created
  2. Workaround: Do not give an untrusted container a writable volume that is also the destination of a tmpcopyup tmpfs.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133553 (Crun: crun: tmpcopyup follows a second path lookup and copies image files onto the host), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133553 (entry last updated 2026-11-20):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
- Red Hat Red Hat Hardened Images: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- A tmpfs mount using tmpcopyup (source: https://access.redhat.com/security/cve/cve-2026-133553)
- A second container sharing a writable volume with the container being created (source: https://access.redhat.com/security/cve/cve-2026-133553)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
Workaround: Do not give an untrusted container a writable volume that is also the destination of a tmpcopyup tmpfs. (source: https://www.cve.org/CVERecord?id=CVE-2026-133553)
CISA KEV: CVE-2026-133553 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133553 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2577547
- https://access.redhat.com/security/cve/CVE-2026-133553
- https://www.cve.org/CVERecord?id=CVE-2026-133553
- https://access.redhat.com/security/cve/cve-2026-133553
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133553
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133553"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Shipped in major Linux distributions
  • Severity7.8/10CVSS 7.8
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133553
RecordNVD · CVE-2026-133553
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2577547
Other links 1
Linkaccess.redhat.com · security/cve/CVE-2026-133553

Questions about CVE-2026-133553

Is CVE-2026-133553 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

When copying files onto a tmpfs mounted with tmpcopyup, crun opens the destination a second time by name. A second container that shares a writable volume with the container being created can change that path between the two lookups, so crun copies image files onto host files, including files under /proc/sys, while running as host root.

Source: access.redhat.com, cve.org

Am I affected, and how do I check?

The checked facts list Red Hat Enterprise Linux 8, 9, and 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4 and 5. The setup involves a tmpfs mount using tmpcopyup and a second container sharing a writable volume with the container being created. Check whether your container configurations use tmpcopyup tmpfs mounts and whether any writable volume is shared between containers.

Source: access.redhat.com, cve.org

How do I fix CVE-2026-133553?

The checked facts name no fixed versions and no vendor patch IDs for this vulnerability, so no upgrade target can be stated from them. Check the vendor advisory for fixed versions or patch IDs for the products listed.

Source: access.redhat.com, cve.org

What if there's no patch?

Do not give an untrusted container a writable volume that is also the destination of a tmpcopyup tmpfs, as the advisory's workaround states.

Source: access.redhat.com, cve.org

No corrections so far. Something wrong on this page? Report an error.