CVE-2026-16460

Bootc: ostree: bootc/ostree: staged deployments not revalidated against container signature policy before finalization

  • High 7.4

Description

A flaw was found in bootc and ostree. Already-staged deployments are finalized without revalidating the deployment's container image against the current containers signature policy. Unsigned OS content staged under a prior permissive policy can remain bootable after policy is hardened to reject unsigned images, leading to full host compromise on reboot.

Key facts

Published
19 Oct 2026
Last changed
4 Nov 2026
Assigned by
redhat
EPSS
0.098% likely to be exploited in the next 30 days, higher than 0.779% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.4CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to revalidate container image signatures against active container signature policy before finalizing or booting staged ostree deployments in bootc and ostree: upgrade to the fixed Bootc/Ostree/Rpm Ostree/Rust Zincati builds, which revalidates container image signatures against the active container signature policy in /etc/containers/policy.json before finalizing or booting already-staged ostree deployments, closing all 2 injection vectors (host reboot into pending staged deployment, bootc upgrade --from-downloaded deployment application). Until patched, this is only a concern on Linux systems using bootc or ostree, including RHEL image-mode hosts — Non-Linux platforms are unaffected — so Clear all existing staged ostree deployments immediately after hardening /etc/containers/policy.json and ensure unsigned container images are never stageCNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 10
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 10
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 8
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 9
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 9
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 9
  • Default status: unaffected
Red HatRed Hat Hardened Images
  • Default status: affected
Red HatRed Hat Hardened Images
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: unaffected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: unaffected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: unaffected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: unaffected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: unaffected

Timeline

  1. 21 Jul 2026 Reported to Red Hat.
  2. 18 Oct 2026 Made public.
  3. 19 Oct 2026 Published

Weakness

References