Medium [CVE-2026-53489] Arbitrary host file read via symlink following in CRI checkpoint restore
This medium-severity Red Hat Linux advisory covers CVE-2026-53489 affecting Red Hat Hardened Images, Red Hat Openshift Data Foundation 4.19, Red Hat Openshift Data Foundation 4.20.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path.
This could result in reading an arbitrary file on the host via kubectl logs. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
This vulnerability, categorized as a Path Traversal (CWE-61), allows an attacker to read arbitrary files on the host system by manipulating symlinked paths during the checkpoint restore process. This can lead to unauthorized information disclosure from the host.
This vulnerability is not exploitable in several Red Hat products listed in the affect table. Although some shipped images include the containerd Go module (primarily v1.x, and in a few cases containerd v2.x API client libraries) as a build-time dependency for OCI image handling, they do not execute the containerd daemon or its CRI plugin.
As a result, the vulnerable containerd CRI checkpoint-restore code path is not exercised. Red Hat severity: Important — CVSS 6.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Weakness: CWE-59.
Affected products named by the advisory: Red Hat Hardened Images; Red Hat Openshift Data Foundation 4.19; Red Hat Openshift Data Foundation 4.20; Exploit Intelligence; and 5 more.
- < 2.3.2
- < 2.2.5
- < 2.1.9
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
- 2.3.2
- 2.2.5
- 2.1.9
- trivy-main-0.69.3-1.2.hum1
- grype-main-0.115.0-0.1.hum1
- syft-main-1.46.0-0.1.hum1
- odf4/cephcsi-rhel9:1786701839
- odf4/cephcsi-rhel9-operator:1786701555
- odf4/mcg-core-rhel9:1786702052
- odf4/mcg-rhel9-operator:1786702559
- odf4/ocs-client-console-rhel9:1786702713
- odf4/ocs-client-rhel9-operator:1786702264
- odf4/ocs-metrics-exporter-rhel9:1786702448
- odf4/ocs-rhel9-operator:1786702276
- odf4/odf-cli-rhel9:1786702440
- odf4/odf-cloudnative-pg-rhel9-operator:1786702315
- odf4/odf-console-rhel9:1786703071
- odf4/odf-cosi-sidecar-rhel9:1786702563
- odf4/odf-csi-addons-rhel9-operator:1786702636
- odf4/odf-csi-addons-sidecar-rhel9:1786702623
- odf4/odf-multicluster-console-rhel9:1786703137
- odf4/odf-multicluster-rhel9-operator:1786702716
- odf4/odf-must-gather-rhel9:1786702872
- odf4/odf-rhel9-operator:1786702949
- odf4/odr-rhel9-operator:1786702917
- odf4/rook-ceph-rhel9-operator:1786703143
- odf4/cephcsi-rhel9:1786627460
- odf4/cephcsi-rhel9-operator:1786626399
- odf4/mcg-core-rhel9:1786628235
- odf4/mcg-rhel9-operator:1786627106
- odf4/ocs-client-console-rhel9:1786629761
- odf4/ocs-client-rhel9-operator:1786627559
- odf4/ocs-metrics-exporter-rhel9:1786687918
- odf4/ocs-rhel9-operator:1786629478
- odf4/odf-cli-rhel9:1786628142
- odf4/odf-cloudnative-pg-rhel9-operator:1786631508
- odf4/odf-console-rhel9:1786628053
- odf4/odf-cosi-sidecar-rhel9:1786627382
- odf4/odf-csi-addons-rhel9-operator:1786627430
- odf4/odf-csi-addons-sidecar-rhel9:1786629076
- odf4/odf-external-snapshotter-rhel9-operator:1786627469
- odf4/odf-external-snapshotter-sidecar-rhel9:1786644072
- odf4/odf-multicluster-console-rhel9:1786688215
- RHSA-2026:15862
- RHSA-2026:32963
- RHSA-2026:32974
- RHSA-2026:56366
- RHSA-2026:57013
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Mitigation checklist
- For Red Hat OpenShift and layered products, CRI-O is the supported container runtime, so the vulnerable containerd CRI checkpoint-restore code path is not exercised during normal cluster operation. Customers should nevertheless apply Red Hat product errata as they become available to receive updates for affected operator, must-gather and tooling images that may bundle the containerd Go module. If containerd is deployed as the container runtime with CRI checkpoint/restore enabled, disable checkpoint/restore functionality until a fixed version of containerd can be applied.
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.