A flaw was found in bootc and ostree on RHEL image-mode hosts. Container signature policy in /etc/containers/policy.json is enforced on image pull and import paths, but already-staged ostree deployments are finalized and booted without revalidation against the current policy. If unsigned OS content was staged while policy was permissive, an administrator who later hardens policy to reject unsigned images can still boot that staged content on the next ordinary reboot or via bootc upgrade --from-downloaded apply paths. This can result in execution of unsigned attacker-controlled OS content as the host root filesystem after believed remediation.