Summary
A privilege-management flaw in crun can cause attacker-controlled content from a container image to execute with host root privileges. The issue becomes risky when crun is built with libkrun and starts a rootful container using passt networking through krun.use_passt.
Affected context
The vulnerability affects deployments using crun with libkrun support when all of the following conditions are present:
- Containers are started in rootful mode.
- Passt networking is enabled through
krun.use_passt. - The container image contains attacker-controlled payload or content that reaches the affected execution path.
The issue is described as a regression beginning in crun 1.29, although actual exposure also depends on build options and runtime configuration.
Exploit preconditions
- Attack surface: Container startup through the crun runtime.
- Required access: The attacker must be able to influence or provide a container image, or otherwise control content consumed from that image.
- Trigger point: Starting a rootful container with libkrun-backed execution and passt networking enabled.
- Why exploitation is possible: An execution path mishandles container-controlled content and can run it with host root privileges rather than preserving the intended container privilege boundary.
Why this happens
The underlying bug is an improper privilege-management condition mapped to CWE-269. A container runtime execution path fails to maintain an appropriate separation between content controlled by the container image and operations performed with host-level privileges. When the affected libkrun and passt configuration is active, attacker-controlled payload can cross the container boundary and execute with excessive authority.
Potential impact
- An attacker could execute code with host root privileges.
- Container isolation could be bypassed.
- The host operating system could be modified or compromised.
- Other containers or workloads could be accessed or disrupted.
- Credentials, secrets, or data available to the host could be exposed.
General mitigation guidance
Mitigation generally focuses on preserving the container-to-host privilege boundary and reducing trust in image content.
Common defensive patterns include:
- Avoiding rootful container execution when rootless operation is practical.
- Disabling or restricting the affected libkrun and passt networking combination unless it is required.
- Using trusted, signed, and reproducibly built container images.
- Applying least-privilege permissions to the runtime, helper processes, and container workloads.
- Separating sensitive workloads from environments that process untrusted images.
- Enforcing container security policies that limit host integration and privileged operations.
- Maintaining runtime components through the organization's standard security patch process without relying on configuration changes alone.
How teams detect issues like this
Organizations can look for this risk through:
- Inventory checks identifying crun builds compiled with libkrun support.
- Runtime policy checks for rootful containers using
krun.use_passt. - Static and configuration analysis that flags privileged container execution and host-integrated networking.
- Code review of runtime changes involving privilege transitions, payload handling, or container startup hooks.
- Audit monitoring for unexpected host-level process creation, filesystem changes, or namespace escapes during container startup.
- Automated container and infrastructure security scanners that evaluate runtime configuration and image provenance.

