# CVE-2026-16460: Bootc: ostree: bootc/ostree: staged deployments not revalidated against container signature policy before finalization

> Attackers can bypass container signature policies to boot unsigned OS content, leading to full host compromise on reboot in Red Hat systems.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-72gj-m9xp-j6qc

## What is CVE-2026-16460?

CVE-2026-16460 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-16460?


## How do I fix CVE-2026-16460?

No fix has been published for CVE-2026-16460 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16460 being exploited?

There is no known exploitation of CVE-2026-16460 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16460 and fix it if it is affected.

What it is: CVE-2026-16460 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16460 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16460/ (Markdown: https://insights.sbomify.com/CVE-2026-16460/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16460
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16460
- OSV: https://osv.dev/vulnerability/CVE-2026-16460

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16460/
Summaries are generated and may contain mistakes; the official description above is the record.