live wire
▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel
upstreambeat.ai
releaseSECURITY

Podman 6.1.3 closes a sandbox bypass by removing checkpoint images from podman run

The security fix is deliberately breaking: checkpoint images can no longer override user-requested container isolation through the normal run path.

Podman 6.1.3 blocks checkpoint images from overriding sandbox settings.
Side by side: what changed
By The Release Desk· Sep 29, 2026the quick take — two AI hosts go live when you do

Podman 6.1.3 removes support for running container checkpoint images through podman run, closing CVE-2026-94603. The project describes the change as both a security fix and a breaking change because the affected checkpoint path could silently replace sandbox settings supplied by the user.

What changed

Podman added OCI distribution of container checkpoints in version 4.4.0, allowing a checkpoint to be pulled from a registry and launched with podman run. Podman identifies those artifacts through the io.podman.annotations.checkpoint.runtime.name image annotation.

The project's security advisory says that once this annotation was present, checkpoint configuration controlled how the container was created. User-provided restrictions could be ignored: the advisory gives podman run --cap-drop=ALL as an example where the checkpoint could instead restore a different capability set. The maintainers concluded that treating checkpoints like ordinary runnable images was inherently unsafe and reverted the feature.

Who it affects

Teams that pull images from registries and depend on command-line sandbox controls should treat the update as security-relevant. The risk is concentrated in images carrying the checkpoint-runtime annotation, but the normal podman run interface did not distinguish that security model clearly enough for callers to rely on their requested restrictions.

The release also affects legitimate workflows that distributed checkpoints as OCI images and launched them with podman run. Podman 6.1.3 intentionally removes that behavior rather than trying to preserve compatibility.

What to do

Users on the 6.1 line should update to 6.1.3 and test any checkpoint-transfer workflow against the removal. Where an immediate update is not possible, the advisory's workaround is to scan pulled images for io.podman.annotations.checkpoint.runtime.name and reject images carrying it. The advisory also warns that Podman cannot currently perform that scan and rejection automatically, so the check must sit elsewhere in the image-admission or pull process.

sources

Filed by The Release Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk