CVE-2024-3154

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 1.4%, top 29% 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
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.2Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity72% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
72%
KEV
Not listed

Published

April 26, 2024

Last Modified

August 24, 2026

Advisory Details (9)

Auto-updated Aug 24, 2026
🔬 Proof of concept available. Patch available. Sources: redhat, github, github_pr.
generic

runtime-spec/features.md at main · opencontainers/runtime-spec · GitHub

https://github.com/opencontainers/runtime-spec/blob/main/features.md#unsafe-annotations-in-configjson
github_pr

features: implement returning potentiallyUnsafeConfigAnnotations list

Fix merged in opencontainers/runc PR #4217 on 2024-03-25 — awaiting tagged release

https://github.com/opencontainers/runc/pull/4217
github Patch Available🟡 PoC Available

arbitrary systemd property injection · Advisory · cri-o/cri-o · GitHub

https://github.com/cri-o/cri-o/security/advisories/GHSA-2cgq-h8xw-2v5j
redhat Patch Available

2272532 – (CVE-2024-3154) CVE-2024-3154 cri-o: Arbitrary command injection via pod annotation

https://bugzilla.redhat.com/show_bug.cgi?id=2272532
redhat Patch Available

CVE-2024-3154 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2024-3154
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:3496
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:2784
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:2672
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:2669

Vendor Advisories for CVE-2024-3154(3)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcri-o-0:1.26.5-16.2.rhaos4.13.git67e2a9d.el82024-06-05redhat
redhatcri-o-0:1.25.5-16.2.rhaos4.12.gitcb09013.el82024-05-16redhat
redhatcri-o-0:1.28.6-2.rhaos4.15.git77bbb1c.el82024-05-09redhat
redhatcri-o-0:1.27.6-2.rhaos4.14.gitb3bd0bf.el82024-05-09redhat

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/cri-o/cri-o—1.29.4—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 31× 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.

Showing the most recent 100 of 183 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-15 03:08 UTCEPSS rescore
  4. 2026-09-15 03:08 UTCEPSS rescore
  5. 2026-09-12 14:59 UTCEPSS rescore
  6. 2026-09-12 10:10 UTCOSV refresh
  7. 2026-09-11 14:51 UTCEPSS rescore
  8. 2026-09-11 09:35 UTCEPSS rescore
  9. 2026-09-08 21:58 UTCEPSS rescore
  10. 2026-09-07 16:00 UTCEPSS rescore
  11. 2026-09-07 15:59 UTCEPSS rescore
  12. 2026-09-06 13:46 UTCEPSS rescore
  13. 2026-09-05 15:26 UTCEPSS rescore
  14. 2026-09-04 13:59 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-02 14:10 UTCEPSS rescore
  17. 2026-09-01 13:52 UTCEPSS rescore
  18. 2026-09-01 04:37 UTCEPSS rescore
  19. 2026-08-30 19:15 UTCEPSS rescore
  20. 2026-08-30 01:20 UTCEPSS rescore
  21. 2026-08-28 21:39 UTCEPSS rescore
  22. 2026-08-27 14:23 UTCEPSS rescore
  23. 2026-08-26 14:44 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-24 15:25 UTCVendor advisory
Show 75 more
  1. 2026-08-24 14:22 UTCEG score recompute
  2. 2026-08-24 14:22 UTCVendor advisory
  3. 2026-08-24 14:15 UTCEPSS rescore
  4. 2026-08-23 00:18 UTCEPSS rescore
  5. 2026-08-21 23:47 UTCEPSS rescore
  6. 2026-08-20 22:53 UTCEPSS rescore
  7. 2026-08-19 17:02 UTCEPSS rescore
  8. 2026-08-18 13:46 UTCEPSS rescore
  9. 2026-08-17 13:45 UTCEPSS rescore
  10. 2026-08-16 14:54 UTCEPSS rescore
  11. 2026-08-16 02:13 UTCEPSS rescore
  12. 2026-08-15 01:28 UTCEPSS rescore
  13. 2026-08-13 21:59 UTCEPSS rescore
  14. 2026-08-13 07:02 UTCOSV refresh
  15. 2026-08-12 13:49 UTCEPSS rescore
  16. 2026-08-11 13:40 UTCEPSS rescore
  17. 2026-08-10 23:58 UTCEPSS rescore
  18. 2026-08-09 13:45 UTCEPSS rescore
  19. 2026-08-08 16:35 UTCEPSS rescore
  20. 2026-08-07 16:25 UTCEPSS rescore
  21. 2026-08-06 13:45 UTCEPSS rescore
  22. 2026-08-05 19:16 UTCEPSS rescore
  23. 2026-08-04 15:08 UTCEPSS rescore
  24. 2026-08-04 10:36 UTCEPSS rescore
  25. 2026-08-03 10:34 UTCEPSS rescore
  26. 2026-08-03 10:34 UTCEPSS rescore
  27. 2026-08-02 02:25 UTCEPSS rescore
  28. 2026-08-01 04:14 UTCEPSS rescore
  29. 2026-08-01 04:14 UTCEPSS rescore
  30. 2026-07-30 16:26 UTCEPSS rescore
  31. 2026-07-30 16:26 UTCEPSS rescore
  32. 2026-07-30 01:29 UTCEPSS rescore
  33. 2026-07-28 15:34 UTCEPSS rescore
  34. 2026-07-28 15:20 UTCOSV refresh
  35. 2026-07-27 14:11 UTCEPSS rescore
  36. 2026-07-26 14:53 UTCEPSS rescore
  37. 2026-07-25 14:16 UTCEPSS rescore
  38. 2026-07-24 14:16 UTCEPSS rescore
  39. 2026-07-23 14:17 UTCEPSS rescore
  40. 2026-07-23 14:17 UTCEPSS rescore
  41. 2026-07-23 02:36 UTCEG score recompute
  42. 2026-07-22 14:07 UTCEPSS rescore
  43. 2026-07-22 14:07 UTCEPSS rescore
  44. 2026-07-21 15:23 UTCEPSS rescore
  45. 2026-07-21 15:23 UTCEPSS rescore
  46. 2026-07-20 17:06 UTCEPSS rescore
  47. 2026-07-19 14:30 UTCEPSS rescore
  48. 2026-07-19 14:30 UTCEPSS rescore
  49. 2026-07-19 02:28 UTCEPSS rescore
  50. 2026-07-19 02:28 UTCEPSS rescore
  51. 2026-07-18 10:03 UTCEPSS rescore
  52. 2026-07-16 17:02 UTCEPSS rescore
  53. 2026-07-15 16:56 UTCEPSS rescore
  54. 2026-07-15 16:56 UTCEPSS rescore
  55. 2026-07-15 01:59 UTCEPSS rescore
  56. 2026-07-15 01:59 UTCEPSS rescore
  57. 2026-07-13 22:29 UTCEPSS rescore
  58. 2026-07-13 06:11 UTCEPSS rescore
  59. 2026-07-12 05:45 UTCEPSS rescore
  60. 2026-07-11 08:26 UTCEPSS rescore
  61. 2026-07-11 08:26 UTCEPSS rescore
  62. 2026-07-11 07:11 UTCOSV refresh
  63. 2026-07-09 19:09 UTCEPSS rescore
  64. 2026-07-08 15:14 UTCEPSS rescore
  65. 2026-07-08 15:13 UTCEPSS rescore
  66. 2026-07-07 13:45 UTCEPSS rescore
  67. 2026-07-06 16:26 UTCEPSS rescore
  68. 2026-07-06 02:22 UTCEPSS rescore
  69. 2026-07-06 02:22 UTCEPSS rescore
  70. 2026-07-05 02:29 UTCEPSS rescore
  71. 2026-07-04 06:30 UTCEPSS rescore
  72. 2026-07-01 15:05 UTCEPSS rescore
  73. 2026-06-30 23:21 UTCEPSS rescore
  74. 2026-06-30 23:21 UTCEPSS rescore
  75. 2026-06-28 14:06 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-3154?
CVE-2024-3154 is a high vulnerability published on April 26, 2024. A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
When was CVE-2024-3154 disclosed?
CVE-2024-3154 was first published in the National Vulnerability Database on April 26, 2024, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-3154 actively exploited?
CVE-2024-3154 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 28.4% of all scored CVEs.
What is the CVSS score of CVE-2024-3154?
CVE-2024-3154 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2024-3154?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3154, 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-2024-3154

Explore →

Is Your Infrastructure Affected by CVE-2024-3154?

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

Start Free Scan →Browse All CVEs