Menu

Star on GitHub · 3.2k

CVE-2026-30892

0.0 · NONE

crun is an open source OCI Container Runtime fully written in C.

Published Mar 26, 2026CWE-269EPSS 0.17%

Overview

CVE-2026-30892 is a none-severity vulnerability. It was published on March 26, 2026 and has a CVSS 3.1 base score of 0.0 (NONE).

This vulnerability has a CVSS 3.1 base score of 0.0, rated NONE. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-30892?

CVE-2026-30892 is a none-severity vulnerability. It was published on March 26, 2026 and has a CVSS 3.1 base score of 0.0 (NONE).

How severe is CVE-2026-30892?

This vulnerability has a CVSS 3.1 base score of 0.0, rated NONE. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-30892?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-30892?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-30892 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related NONE CVEs from 2026

View all