CVE-2025-52881Published

runc: LSM labels can be bypassed with malicious config using dummy procfs files

Collected exploitation and prediction evidence

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

cve-program · CVE-2025-52881

Published

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7, 1.3.2 and 1.4.0-rc.2, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.

Source published: 6 Nov 2025 20:23:36 UTC
Source modified: 6 Nov 2025 21:07:09 UTC
Observed here: 23 Oct 2026 15:48:27 UTC
Source terms: CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 4.0 · 7.3 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

euvd · EUVD-2025-37940

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 6, 2025, 8:23:36 PM

dateUpdated: Nov 6, 2025, 9:07:09 PM

105 related source bulletins · separate from aliases

WID-SEC-W-2025-2518: Red Hat Enterprise Linux (runc): Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:61629: Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (ROCm)

CVE-2025-52881 · CVE-2025-66418 · CVE-2026-0994 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-40192 · CVE-2026-41523 · CVE-2026-44222 · CVE-2026-48586 · CVE-2026-48746 · CVE-2026-54060 · CVE-2026-54234 · CVE-2026-54235 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-55574 · CVE-2026-55969 · CVE-2026-56208 · CVE-2026-56209 · CVE-2026-56210 · CVE-2026-56211 · CVE-2026-58049 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-64830 · CVE-2026-64835

RHSA-2026:4531: Red Hat Security Advisory: runc security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-65637

RHSA-2026:0676: Red Hat Security Advisory: OpenShift Container Platform 4.13.63 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2025:22012: Red Hat Security Advisory: buildah security update

CVE-2025-52881 · CVE-2025-58183

SUSE-SU-2025:3951-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:19244: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.14.32 security, enhancement & bug fix update

CVE-2025-52881

RHSA-2026:1942: Red Hat Security Advisory: Red Hat Quay 3.15.3

CVE-2024-34156 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-47907 · CVE-2025-47913 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-59420 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

RHSA-2026:2951: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection

CVE-2025-47907 · CVE-2025-52881 · CVE-2025-61729

RHSA-2026:0050: Red Hat Security Advisory: Red Hat OpenShift Builds 1.6.2

CVE-2025-52881 · CVE-2025-66418

RHSA-2026:0424: Red Hat Security Advisory: podman security update

CVE-2025-52881 · CVE-2025-58183

RHSA-2026:0418: Red Hat Security Advisory: OpenShift Container Platform 4.16.55 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:2343: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection

CVE-2024-25621 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-61729

RHSA-2025:22030: Red Hat Security Advisory: podman security update

CVE-2025-52881 · CVE-2025-58183

RHSA-2025:21328: Red Hat Security Advisory: OpenShift Container Platform 4.14.59 packages and security update

CVE-2025-22871 · CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2025:22275: Red Hat Security Advisory: OpenShift Container Platform 4.13.62 bug fix and security update

CVE-2025-4953 · CVE-2025-5318 · CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:39894: Red Hat Security Advisory: Release of containers for RHOSO 18.0.21

CVE-2025-52881 · CVE-2026-23490 · CVE-2026-32280

WID-SEC-W-2026-3046: IBM Concert: Mehrere Schwachstellen

CVE-2019-19921 · CVE-2021-23337 · CVE-2024-3651 · CVE-2024-39338 · CVE-2024-45590 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-15599 · CVE-2025-22874 · CVE-2025-47273 · CVE-2025-47907 · CVE-2025-52881 · CVE-2025-53643 · CVE-2025-55184 · CVE-2025-58056 · CVE-2025-58188 · CVE-2025-58189 · CVE-2025-61723 · CVE-2025-61730 · CVE-2025-64649 · CVE-2025-64756 · CVE-2025-67221 · CVE-2025-68121 · CVE-2025-68146 · CVE-2026-0540 · CVE-2026-2327 · CVE-2026-23490 · CVE-2026-23897 · CVE-2026-2391 · CVE-2026-23949 · CVE-2026-24486 · CVE-2026-25528 · CVE-2026-25547 · CVE-2026-25639 · CVE-2026-25990 · CVE-2026-26007 · CVE-2026-26019 · CVE-2026-26996 · CVE-2026-27142 · CVE-2026-27212 · CVE-2026-27699 · CVE-2026-27903 · CVE-2026-27904 · CVE-2026-28684 · CVE-2026-29063 · CVE-2026-29181 · CVE-2026-2950 · CVE-2026-31808 · CVE-2026-31900 · CVE-2026-32274 · CVE-2026-32288 · CVE-2026-32597 · CVE-2026-32630 · CVE-2026-32887 · CVE-2026-32952 · CVE-2026-33186 · CVE-2026-33532 · CVE-2026-33750 · CVE-2026-33814 · CVE-2026-33816 · CVE-2026-33916 · CVE-2026-34043 · CVE-2026-34073 · CVE-2026-34077 · CVE-2026-3520 · CVE-2026-35469 · CVE-2026-35515 · CVE-2026-3627 · CVE-2026-39823 · CVE-2026-39825 · CVE-2026-39826 · CVE-2026-39892 · CVE-2026-39984 · CVE-2026-40175 · CVE-2026-40179 · CVE-2026-40181 · CVE-2026-40190 · CVE-2026-40347 · CVE-2026-41066 · CVE-2026-41182 · CVE-2026-41238 · CVE-2026-41239 · CVE-2026-41240 · CVE-2026-41305 · CVE-2026-41324 · CVE-2026-41425 · CVE-2026-41481 · CVE-2026-41488 · CVE-2026-41602 · CVE-2026-41636 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42198 · CVE-2026-42211 · CVE-2026-42338 · CVE-2026-42342 · CVE-2026-42561 · CVE-2026-42577 · CVE-2026-43870 · CVE-2026-44405 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44496 · CVE-2026-44728 · CVE-2026-4539 · CVE-2026-45409 · CVE-2026-45736 · CVE-2026-46625 · CVE-2026-4800 · CVE-2026-4923 · CVE-2026-4926 · CVE-2026-7246 · CVE-2026-8723

RHSA-2025:19927: Red Hat Security Advisory: runc security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:4073-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:4077-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:21038-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:72851: Red Hat Security Advisory: multicluster engine for Kubernetes v2.9.8 security update

CVE-2025-52881 · CVE-2026-25681 · CVE-2026-33818 · CVE-2026-39829 · CVE-2026-41178 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59879 · CVE-2026-73500 · CVE-2026-84445

RHSA-2026:2975: Red Hat Security Advisory: OpenShift Container Platform 4.18.34 packages and security update

CVE-2025-52881

RHSA-2026:0701: Red Hat Security Advisory: OpenShift Container Platform 4.17.47 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:4081-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2026:22451-1: Security update for podman

CVE-2025-22869 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566 · CVE-2026-34986 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598

RHSA-2026:4215: Red Hat Security Advisory: Red Hat Quay 3.14.6

CVE-2022-30187 · CVE-2024-34156 · CVE-2024-47081 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-45768 · CVE-2025-47273 · CVE-2025-47913 · CVE-2025-50181 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-59420 · CVE-2025-61729 · CVE-2025-61920 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

RHSA-2026:2034: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.20 security, enhancement & bug fix update

CVE-2025-52881

SUSE-SU-2025:4073-2: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2026:20123-1: Security update for buildah

CVE-2025-31133 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:3950-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:0315: Red Hat Security Advisory: OpenShift Container Platform 4.12.84 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

openSUSE-SU-2025-20072-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:3713: Red Hat Security Advisory: RHOAI 3.3 - Red Hat OpenShift AI

CVE-2024-25621 · CVE-2025-6242 · CVE-2025-12638 · CVE-2025-12816 · CVE-2025-14180 · CVE-2025-14920 · CVE-2025-14921 · CVE-2025-14922 · CVE-2025-14924 · CVE-2025-14925 · CVE-2025-14926 · CVE-2025-14927 · CVE-2025-14928 · CVE-2025-14929 · CVE-2025-14930 · CVE-2025-15284 · CVE-2025-48956 · CVE-2025-52881 · CVE-2025-59425 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62164 · CVE-2025-62593 · CVE-2025-64756 · CVE-2025-66031 · CVE-2025-66034 · CVE-2025-66416 · CVE-2025-66418 · CVE-2025-66448 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-66626 · CVE-2025-67725 · CVE-2025-67726 · CVE-2025-68156 · CVE-2025-68476 · CVE-2025-68665 · CVE-2025-69223 · CVE-2025-69872 · CVE-2026-0897 · CVE-2026-1260 · CVE-2026-21441 · CVE-2026-22778 · CVE-2026-22807 · CVE-2026-24049 · CVE-2026-24486

openSUSE-SU-2026:20080-1: Security update for buildah

CVE-2025-31133 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52565 · CVE-2025-52881

msrc_CVE-2025-52881: runc: LSM labels can be bypassed with malicious config using dummy procfs files

CVE-2025-52881

SUSE-SU-2025:4076-1: Security update for buildah

CVE-2025-52881

SUSE-SU-2025:4075-1: Security update for buildah

CVE-2025-52881

RHBA-2025:21224: Red Hat Bug Fix Advisory: OpenShift Container Platform 4.20.4 bug fix update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:1730: Red Hat Security Advisory: Red Hat Quay 3.12.13

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441

RHSA-2026:8325: Red Hat Security Advisory: buildah, crun, podman, runc, and skopeo security update

CVE-2025-31133 · CVE-2025-47913 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-65637

SUSE-SU-2026:21291-1: Security update for podman

CVE-2025-31133 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52565 · CVE-2025-52881

RHSA-2025:21220: Red Hat Security Advisory: podman security update

CVE-2025-52881

RHSA-2026:4185: Red Hat Security Advisory: Red Hat Quay 3.13.11

CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

SUSE-SU-2026:22516-1: Security update for podman

CVE-2024-6104 · CVE-2025-22869 · CVE-2025-27144 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566 · CVE-2026-34986 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598

RHSA-2026:0331: Red Hat Security Advisory: OpenShift Container Platform 4.18.31 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:2754: Red Hat Security Advisory: Red Hat Quay 3.9.18

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-52881 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66506 · CVE-2026-24049

SUSE-SU-2025:4080-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2025:21633: Red Hat Security Advisory: buildah security update

CVE-2025-52881

SUSE-SU-2025:21036-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:4079-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2026:20626-1: Security update for podman

CVE-2025-22869 · CVE-2025-31133 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566

RHSA-2026:0426: Red Hat Security Advisory: buildah security update

CVE-2025-52881 · CVE-2025-58183

RHSA-2026:2681: Red Hat Security Advisory: Red Hat Quay 3.16.2

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-15284 · CVE-2025-31133 · CVE-2025-52881 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441 · CVE-2026-24049

RHSA-2025:21232: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:10703: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2025-31133 · CVE-2025-47913 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-65637

SUSE-SU-2026:20116-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-9566

RHSA-2025:21795: Red Hat Security Advisory: OpenShift Container Platform 4.18.29 bug fix and security update

CVE-2025-11561 · CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:41928: Red Hat Security Advisory: Red Hat Migration Toolkit for Containers

CVE-2025-7783 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62718 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-68121 · CVE-2025-69223 · CVE-2025-69227 · CVE-2025-69228 · CVE-2026-4800 · CVE-2026-6322 · CVE-2026-9277 · CVE-2026-9595 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-21441 · CVE-2026-22029 · CVE-2026-23490 · CVE-2026-23745 · CVE-2026-25679 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27137 · CVE-2026-29063 · CVE-2026-30922 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32283 · CVE-2026-33186 · CVE-2026-33810 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-40895 · CVE-2026-42264 · CVE-2026-42338 · CVE-2026-42499 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45736 · CVE-2026-45822 · CVE-2026-48779

SUSE-SU-2025:21054-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:37387: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update

CVE-2024-25621 · CVE-2024-40635 · CVE-2024-45310 · CVE-2025-8766 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22870 · CVE-2025-47911 · CVE-2025-52881 · CVE-2025-54410 · CVE-2025-58058 · CVE-2025-64329 · CVE-2025-66506 · CVE-2026-22772 · CVE-2026-23831 · CVE-2026-24117 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-25934 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27903 · CVE-2026-33540 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35172 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39883 · CVE-2026-41506 · CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-45571 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598

RHSA-2026:61628: Red Hat Security Advisory: Red Hat AI Inference Server Model Optimization Tools 3.2.2 (CUDA)

CVE-2025-52881 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-69223 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-21441 · CVE-2026-24049 · CVE-2026-25087 · CVE-2026-28684 · CVE-2026-40192 · CVE-2026-42311 · CVE-2026-48586 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-55969 · CVE-2026-56208 · CVE-2026-56209 · CVE-2026-56210 · CVE-2026-56211 · CVE-2026-58049 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-64830 · CVE-2026-64835

RHSA-2026:8433: Red Hat Security Advisory: OpenShift Compliance Operator bug fix and enhancement update

CVE-2025-52881 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-68121 · CVE-2026-4645 · CVE-2026-25679 · CVE-2026-33186

RHSA-2025:21824: Red Hat Security Advisory: OpenShift Container Platform 4.16.53 bug fix and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

openSUSE-SU-2025:15705-1: runc-1.3.3-1.1 on GA media

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:3391: Red Hat Security Advisory: OpenShift Container Platform 4.19.25 packages and security update

CVE-2025-52881 · CVE-2025-61726

RHSA-2026:0425: Red Hat Security Advisory: runc security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-65637

SUSE-SU-2026:0327-1: Security update for alloy

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-68156

RHSA-2025:23347: Red Hat Security Advisory: podman security update

CVE-2025-52881 · CVE-2025-58183

RHBA-2025:21361: Red Hat Bug Fix Advisory: OpenShift Container Platform 4.19.19 packages update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2025:20957: Red Hat Security Advisory: runc security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2026:20103-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-9566

RHSA-2025:21702: Red Hat Security Advisory: podman security update

CVE-2025-52881

openSUSE-SU-2025:15843-1: buildah-1.42.2-1.1 on GA media

CVE-2025-52881

RHSA-2025:22011: Red Hat Security Advisory: buildah security update

CVE-2025-52881 · CVE-2025-58183

RHSA-2026:0995: Red Hat Security Advisory: OpenShift Container Platform 4.14.61 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

openSUSE-SU-2026:20140-1: Security update for alloy

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-68156

SUSE-SU-2026:24378-1: Security update for podman

CVE-2025-22869 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566 · CVE-2026-34986 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-42508 · CVE-2026-55686 · CVE-2026-57231

RHSA-2025:21634: Red Hat Security Advisory: buildah security update

CVE-2025-52881

SUSE-SU-2025:4074-1: Security update for buildah

CVE-2025-52881

openSUSE-SU-2026:20305-1: Security update for podman

CVE-2025-22869 · CVE-2025-31133 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566

RHSA-2026:2762: Red Hat Security Advisory: Red Hat Quay 3.10.18

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

SUSE-SU-2026:20214-1: Security update for alloy

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-68156

RHSA-2026:2900: Red Hat Security Advisory: Network Observability 1.11.0 for OpenShift

CVE-2024-25621 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-64329 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-23745 · CVE-2026-24049 · CVE-2026-24842

RHSA-2025:23543: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2025-52881

RHSA-2026:2106: Red Hat Security Advisory: RHOAI 2.25.2 - Red Hat OpenShift AI

CVE-2025-12805 · CVE-2025-12816 · CVE-2025-52881 · CVE-2025-66034 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-66626 · CVE-2025-67725 · CVE-2025-67726 · CVE-2025-68156 · CVE-2025-68476 · CVE-2025-69223 · CVE-2026-21441 · CVE-2026-24049

SUSE-SU-2025:21136-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

RHSA-2026:61627: Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (CUDA)

CVE-2025-52881 · CVE-2025-62593 · CVE-2025-66418 · CVE-2026-0994 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-40192 · CVE-2026-41523 · CVE-2026-44222 · CVE-2026-48586 · CVE-2026-48746 · CVE-2026-50193 · CVE-2026-54060 · CVE-2026-54234 · CVE-2026-54235 · CVE-2026-54283 · CVE-2026-54399 · CVE-2026-54512 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-55574 · CVE-2026-55969 · CVE-2026-56208 · CVE-2026-56209 · CVE-2026-56210 · CVE-2026-56211 · CVE-2026-57516 · CVE-2026-58049 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-64830 · CVE-2026-64835

RHSA-2026:4693: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2024-45336 · CVE-2025-22866 · CVE-2025-31133 · CVE-2025-47913 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-65637

RHSA-2026:1540: Red Hat Security Advisory: OpenShift Container Platform 4.15.61 packages and security update

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-65637

RHSA-2026:4532: Red Hat Security Advisory: buildah security update

CVE-2025-47913 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-65637

RHSA-2026:3416: Red Hat Security Advisory: OpenShift Container Platform 4.17.50 packages and security update

CVE-2025-52881 · CVE-2025-61726

RHSA-2026:0316: Red Hat Security Advisory: OpenShift Container Platform 4.12.84 bug fix and security update

CVE-2025-4953 · CVE-2025-8677 · CVE-2025-11561 · CVE-2025-40778 · CVE-2025-40780 · CVE-2025-52881 · CVE-2025-59375

RHSA-2025:23113: Red Hat Security Advisory: OpenShift Container Platform 4.15.60 bug fix and security update

CVE-2025-4953 · CVE-2025-11561 · CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

openSUSE-SU-2026:21244-1: Security update for podman

openSUSE-SU-2026:20072-1: Security update for podman

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-9566

openSUSE-SU-2025:15721-1: incus-6.17-2.1 on GA media

CVE-2025-52881

openSUSE-SU-2025:20072-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

SUSE-SU-2025:21072-1: Security update for runc

CVE-2025-31133 · CVE-2025-52565 · CVE-2025-52881

openSUSE-SU-2025:15845-1: podman-5.7.1-1.1 on GA media

CVE-2025-52881 · CVE-2025-9566

RHSA-2026:2695: Red Hat Security Advisory: RHOAI 2.25.2 - Red Hat OpenShift AI

CVE-2025-12805 · CVE-2025-12816 · CVE-2025-14925 · CVE-2025-52881 · CVE-2025-66034 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-66626 · CVE-2025-68156 · CVE-2025-68476 · CVE-2025-69223 · CVE-2026-21441 · CVE-2026-24049

SUSE-SU-2026:20641-1: Security update for podman

CVE-2025-22869 · CVE-2025-31133 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566

RHSA-2026:4533: Red Hat Security Advisory: podman security update

CVE-2025-52881 · CVE-2025-58183 · CVE-2025-65637

RHSA-2026:2456: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.26.0 Release.

CVE-2024-25621 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-61729 · CVE-2025-64756 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66490 · CVE-2026-21441 · CVE-2026-22029

Source published: Nov 6, 2025, 8:23:36 PM (timezone not stated)
Source modified: Nov 6, 2025, 9:07:09 PM (timezone not stated)
Observed here: 11 Nov 2026 03:31:11 UTC
Source terms: ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.

EUVD CVSS 4.0 · 7.3 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

nvd · CVE-2025-52881

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-61 · CWE-363

Original publisher date fields

published: 2025-11-06T21:15:42.817

lastModified: 2026-10-07T21:10:00.200

3 source CPE criteria · context only

cpe:2.3:a:linuxfoundation:runc:*:*:*:*:*:*:*:*
cpe:2.3:a:linuxfoundation:runc:1.4.0:rc1:*:*:*:*:*:*
cpe:2.3:a:linuxfoundation:runc:1.4.0:rc2:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published: 6 Nov 2025 21:15:42 UTC
Source modified: 7 Oct 2026 21:10:00 UTC
Observed here: 25 Oct 2026 02:25:01 UTC
Source terms: NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 4.0 · [email protected] · Secondary · 7.3 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

osv · GHSA-cgrx-mc8f-2prm

Published

### Impact ### This attack is primarily a more sophisticated version of CVE-2019-19921, which was a flaw which allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy `tmpfs` file and thus not apply the correct LSM labels to the container process. The mitigation runc applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when runc writes LSM labels that those labels are actual procfs files. Rather than using a fake `tmpfs` file for `/proc/self/attr/<label>`, an attacker could instead (through various means) make `/proc/self/attr/<label>` reference a real `procfs` file, but one that would still be a no-op (such as `/proc/self/sched`). This would have the same effect but would clear the "is a procfs file" check. Runc is aware that this kind of attack would be possible (even going so far as to discuss this publicly as "future work" at conferences), and runc is working on a far more comprehensive mitigation of this attack, but this security issue was disclosed before runc could complete this work. In all known versions of runc, an attacker can trick runc into misdirecting writes to `/proc` to other procfs files through the use of a racing container with shared mounts (runc has also verified this attack is possible to exploit using a standard Dockerfile with `docker buildx build` as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a `tmpfs` or theoretically other methods such as regular bind-mounts. Note that while `/proc/self/attr/<label>` was the example used above (which is LSM-specific), this issue affect all writes to `/proc` in runc and thus also affects sysctls (written to `/proc/sys/...`) and some other APIs. #### Additional Impacts #### While investigating this issue, runc discovered that another risk with these redirected writes is that they could be redirected to dangerous files such as `/proc/sysrq-trigger` rather than just no-op files like `/proc/self/sched`. For instance, the default AppArmor profile name in Docker is `docker-default`, which when written to `/proc/sysrq-trigger` would cause the host system to crash. When this was discovered, runc conducted an audit of other write operations within runc and found several possible areas where runc could be used as a semi-arbitrary write gadget when combined with the above race attacks. The most concerning attack scenario was the configuration of sysctls. Because the contents of the sysctl are free-form text, an attacker could use a misdirected write to write to `/proc/sys/kernel/core_pattern` and break out of the container (as described in CVE-2025-31133, kernel upcalls are not namespaced and so coredump helpers will run with complete root privileges on the host). Even if the attacker cannot configure custom sysctls, a valid sysctl string (when redirected to `/proc/sysrq-trigger`) can easily cause the machine to hang. Note that the fact that this attack allows you to disable LSM labels makes it a very useful attack to combine with CVE-2025-31133 (as one of the only mitigations available to most users for that issue is AppArmor, and this attack would let you bypass that). However, the misdirected write issue above means that you could also achieve most of the same goals without needing to chain together attacks. ### Patches ### This advisory is being published as part of a set of three advisories: * CVE-2025-31133 * CVE-2025-52881 * CVE-2025-52565 The patches fixing this issue have accordingly been combined into a single patchset. The following patches from that patchset resolve the issues in this advisory: * db19bbed5348 ("internal/sys: add VerifyInode helper") * 6fc191449109 ("internal: move utils.MkdirAllInRoot to internal/pathrs") * ff94f9991bd3 ("*: switch to safer securejoin.Reopen") * 44a0fcf685db ("go.mod: update to github.com/cyphar/[email protected]") * 77889b56db93 ("internal: add wrappers for securejoin.Proc*") * fdcc9d3cad2f ("apparmor: use safe procfs API for labels") * ff6fe1324663 ("utils: use safe procfs for /proc/self/fd loop code") * b3dd1bc562ed ("utils: remove unneeded EnsureProcHandle") * 77d217c7c377 ("init: write sysctls using safe procfs API") * 435cc81be6b7 ("init: use securejoin for /proc/self/setgroups") * d61fd29d854b ("libct/system: use securejoin for /proc/$pid/stat") * 4b37cd93f86e ("libct: align param type for mountCgroupV1/V2 functions") * d40b3439a961 ("rootfs: switch to fd-based handling of mountpoint targets") * ed6b1693b8b3 ("selinux: use safe procfs API for labels") - Please note that this patch includes a private patch for `github.com/opencontainers/selinux` that could not be made public through a public pull request (as it would necessarily disclose this embargoed security issue). The patch includes a complete copy of the forked code and a `replace` directive (as well as `go mod vendor` applied), which should still work with downstream build systems. If you cannot apply this patch, you can safely drop it -- some of the other patches in this series should block these kinds of racing mount attacks entirely. See https://github.com/opencontainers/selinux/pull/237 for the upstream patch. * 3f925525b44d ("rootfs: re-allow dangling symlinks in mount targets") * a41366e74080 ("openat2: improve resilience on busy systems") runc 1.2.8, 1.3.3, and 1.4.0-rc.3 have been released and all contain fixes for these issues. As per [runc's new release model][RELEASES.md], runc 1.1.x and earlier are no longer supported and thus have not been patched. [CVE-2025-31133]: https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2 [CVE-2025-52565]: https://github.com/opencontainers/runc/security/advisories/GHSA-qw9x-cqr3-wc7r [CVE-2025-52881]: https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm [RELEASES.md]: https://github.com/opencontainers/runc/blob/v1.4.0-rc.2/RELEASES.md ### Mitigations ### * Do not run untrusted container images from unknown or unverified sources. * For the basic no-op attack, this attack allows a container process to run with the same LSM labels as `runc`. For most AppArmor deployments this means it will be `unconfined`, and for SELinux it will likely be `container_runtime_t`. Runc has not conducted in-depth testing of the impact on SELinux -- it is possible that it provides some reasonable protection but it seems likely that an attacker could cause harm to systems even with such an SELinux setup. * For the more involved redirect and write gadget attacks, unfortunately most LSM profiles (including the standard container-selinux profiles) provide the container runtime access to sysctl files (including `/proc/sysrq-trigger`) and so LSMs likely do not provide much protection against these attacks. * Using rootless containers provides some protection against these kinds of bugs (privileged writes in runc being redirected) -- by having runc itself be an unprivileged process, in general you would expect the impact scope of a runc bug to be less severe as it would only have the privileges afforded to the host user which spawned runc. For this particular bug, the privilege escalation caused by the inadvertent write issue is entirely mitigated with rootless containers because the unprivileged user that the `runc` process is executing as cannot write to the aforementioned procfs files (even intentionally). ### Other Runtimes ### As this vulnerability boils down to a fairly easy-to-make logic bug, runc has provided information to other OCI (crun, youki) and non-OCI (LXC) container runtimes about this vulnerability. Based on discussions with other runtimes, it seems that crun and youki may have similar security issues and will release a co-ordinated security release along with runc. LXC appears to use the host's `/proc` for all procfs operations, and so is likely not vulnerable to this issue (this is a trade-off -- runc uses the container's procfs to avoid CVE-2016-9962-style attacks). [CVE-2016-9962]: https://seclists.org/fulldisclosure/2017/Jan/21 ### Credits ### Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering this vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions. Additional thanks go to Tõnis Tiigi for finding some very useful exploit templates for these kinds of race attacks using `docker buildx build`.

Source published: 5 Nov 2025 18:40:40 UTC
Source modified: 10 Sep 2026 03:50:30 UTC
Observed here: 24 Oct 2026 13:19:41 UTC
Source terms: GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V4 · CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Publisher rating · HIGH

osv · GO-2025-4098

Published

Container escape and DDoS due to arbitrary write gadgets and procfs write redirects in github.com/opencontainers/runc

Source published: 18 Nov 2025 15:44:15 UTC
Source modified: 4 Feb 2026 02:52:46 UTC
Observed here: 24 Oct 2026 13:19:41 UTC
Source terms: OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.