Privilege escalation via skipped UID assignment
Published Mar 25, 2026 · Updated Mar 26, 2026
Privilege escalation in Containers crun 1.19 through 1.26 allows local users to run crun exec processes as UID 0 via --user 1. The make_oci_process_user function returns a newly allocated user object before assigning the parsed UID when USERSPEC contains only a UID, leaving the UID at its zero-initialized value. Exploitation requires permission to invoke crun exec against a running container and grants UID 0 within that execution context rather than the requested UID 1.
Summary
What happened
Privilege escalation in Containers crun 1.19 through 1.26 allows local users to run crun exec processes as UID 0 via --user 1. The make_oci_process_user function returns a newly allocated user object before assigning the parsed UID when USERSPEC contains only a UID, leaving the UID at its zero-initialized value. Exploitation requires permission to invoke crun exec against a running container and grants UID 0 within that execution context rather than the requested UID 1.
The record
- CVE
- CVE-2026-30892
- Published
- Mar 25, 2026
- Updated
- Mar 26, 2026
- Vendor
- Containers
- Product
- crun
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.19, < 1.27
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream crun exec --user 1 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo