CVE-2026-30892

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

March 25, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github Patch Available🟡 PoC Available

Incorrectly parsed `crun exec` option `-u` leads to privilege escalation · Advisory · containers/crun · GitHub

https://github.com/containers/crun/security/advisories/GHSA-4vg2-xjqj-7chj
github_release Patch Available

1.27

Patch available: containers/crun 1.27

https://github.com/containers/crun/releases/tag/1.27
github_commit

commit 1bd7f4244699 (containers/crun)

Fix landed in containers/crun commit 1bd7f4244699 — awaiting tagged release

https://github.com/containers/crun/commit/1bd7f42446999b0e76bc3d575392e05c943b0b01

Vendor Advisories for CVE-2026-30892(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcrun-0:1.27.1-1.el10_02026-07-29redhat
redhatrhcos-4.19.9.6.202606302000-02026-07-09redhat
redhatcrun-0:1.27-1.el9_62026-06-22redhat
redhatcrun-0:1.27-1.el9_82026-05-19redhat
redhatcrun-0:1.27-2.el10_22026-05-19redhat
redhatcrun-0:1.27-1.el9_72026-04-06redhat
redhatcrun-0:1.27-1.el10_12026-04-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
crun1.21-1 ... 1.28-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
crun1.21-1, 1.21-2, 1.21-3, 1.24-1, 1.26-11.27-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-02 14:01 UTCOSV refresh
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 50 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 10:12 UTCEG score recompute
  5. 2026-08-16 10:12 UTCVendor advisory
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 19:29 UTCVendor advisory
  9. 2026-08-14 06:30 UTCEG score recompute
  10. 2026-08-14 06:30 UTCVendor advisory
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 20:47 UTCEG score recompute
  13. 2026-08-12 20:47 UTCVendor advisory
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 20:52 UTCVendor advisory
  16. 2026-08-11 03:54 UTCEG score recompute
  17. 2026-08-11 03:54 UTCVendor advisory
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 07:50 UTCVendor advisory
  20. 2026-08-09 18:56 UTCEG score recompute
  21. 2026-08-09 18:56 UTCVendor advisory
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 06:03 UTCEG score recompute
  24. 2026-08-09 06:03 UTCVendor advisory
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 05:20 UTCEG score recompute
  27. 2026-08-08 05:20 UTCVendor advisory
  28. 2026-08-07 16:26 UTCVendor advisory
  29. 2026-08-06 18:50 UTCEG score recompute
  30. 2026-08-06 18:50 UTCVendor advisory
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 00:55 UTCEG score recompute
  33. 2026-08-06 00:55 UTCVendor advisory
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-04 15:10 UTCEPSS rescore
  36. 2026-08-03 23:39 UTCEG score recompute
  37. 2026-08-03 23:39 UTCVendor advisory
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-02 15:26 UTCEG score recompute
  40. 2026-08-02 15:26 UTCVendor advisory
  41. 2026-08-02 02:26 UTCEPSS rescore
  42. 2026-08-01 04:16 UTCEPSS rescore
  43. 2026-07-30 16:27 UTCEPSS rescore
  44. 2026-07-30 01:30 UTCEPSS rescore
  45. 2026-07-28 15:36 UTCEPSS rescore
  46. 2026-07-27 14:46 UTCEG score recompute▲ 7.80
  47. 2026-07-27 14:46 UTCVendor advisory
  48. 2026-07-27 12:56 UTCEG score recompute
  49. 2026-07-27 12:56 UTCVendor advisory
  50. 2026-07-27 12:50 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-30892?
CVE-2026-30892 is a high vulnerability published on March 25, 2026. 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.…
When was CVE-2026-30892 disclosed?
CVE-2026-30892 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-30892 actively exploited?
CVE-2026-30892 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-30892?
CVE-2026-30892 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-30892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-30892, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-30892

Explore →

Is Your Infrastructure Affected by CVE-2026-30892?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs