---
id: "CVE-2026-16460"
kind: "vulnerability"
aliases: ["CVE-2026-16460"]
title: "bootc and ostree: staged deployments skip signature re-check before reboot"
severity: "high"
cvss: 7.4
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "bootc", "fixed": [], "affected": "unknown", "ecosystem": "vendor"}, {"name": "ostree", "fixed": [], "affected": "unknown", "ecosystem": "vendor"}]
ecosystems: []
tags: ["bootc", "image-mode", "infrastructure", "linux", "ostree", "rhel", "self-hosted"]
not_affected_if: ["no-permissive-policy-history", "no-staged-deployments", "policy-hardened-before-first-stage"]
published_at: "2026-10-19T07:16:31+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T03:42:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-16460", "first_seen_at": "2026-10-23T21:57:17+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-25T03:42:29+00:00"}]
---

# bootc and ostree: staged deployments skip signature re-check before reboot

bootc and ostree finalize already-staged OS deployments without rechecking the container image against the current signature policy. Unsigned OS content staged under an older, permissive policy can still boot after the policy is tightened, which gives an attacker full host compromise on reboot.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:bootc affected unknown fixed ?
- vendor:ostree affected unknown fixed ?

## How to check

On bootc/ostree hosts run 'bootc status' (and 'ostree admin status') and look for a staged deployment; if one exists and was pulled while /etc/containers/policy.json allowed unsigned images, treat as exposed. Compare installed bootc/ostree package versions against Red Hat's errata once published (none yet).

## Fix

No fixed version published yet (unknown; Red Hat says upgrade to fixed bootc/ostree builds when released). Interim: after tightening /etc/containers/policy.json, discard any staged deployment (re-run 'bootc upgrade' so it restages under the new policy, or 'ostree admin undeploy' the pending one) before rebooting, and never stage unsigned images.

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-16460
- 2026-10-25T03:42:29+00:00 analyst — Read Red Hat CVE page (CNA): local, high complexity, no fixed versions or errata published; RHEL 8/10 listed not affected per aggregators, Hardened Images/OpenShift affected. No exploitation or PoC seen. Upstream bootc fix commit not found.

## Documents

- [advisory] Red Hat CVE-2026-16460 https://access.redhat.com/security/cve/CVE-2026-16460
- [mentions] bootc security and threat model https://bootc.dev/bootc/bootc-security.7.html

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_