Cri-o: arbitrary command injection via pod annotation (CVE-2024-3154)

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Apr 26, 2024
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 24, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.