CVE-2025-52881

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
40.6%
KEV
Not listed

Published

November 6, 2025

Last Modified

December 3, 2025

References (20)

Vendor Advisories for CVE-2025-52881(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17787974462026-05-19redhat
redhatcontainer-tools:rhel8-8060020260422144418.ad008a3a2026-04-27redhat
redhatcompliance/openshift-compliance-must-gather-rhel8:17756413442026-04-16redhat
redhatrunc-4:1.2.9-1.el9_02026-04-15redhat
redhatcontainer-tools:rhel8-8080020260226135022.63b345852026-03-17redhat
redhatrunc-4:1.2.9-1.el9_2.12026-03-12redhat
redhatbuildah-1:1.29.5-1.el9_2.22026-03-12redhat
redhatpodman-2:4.4.1-22.el9_2.52026-03-12redhat
redhatquay/quay-rhel8:17730888622026-03-10redhat
redhatquay/quay-rhel8:17730976212026-03-10redhat
redhatbuildah-2:1.33.12-3.rhaos4.17.el82026-03-04redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17718741812026-03-04redhat
redhatbuildah-2:1.33.12-4.rhaos4.19.el92026-03-04redhat
redhatbuildah-2:1.33.12-2.rhaos4.18.el92026-02-25redhat
redhatnetwork-observability/network-observability-cli-rhel9:17712260602026-02-18redhat
redhatoadp/oadp-velero-plugin-rhel9:17706435542026-02-18redhat
redhatquay/quay-rhel8:17708561032026-02-16redhat
redhatquay/quay-rhel8:17702491832026-02-16redhat
redhatrhoai/odh-model-registry-job-async-upload-rhel9:17703588472026-02-12redhat
redhatquay/quay-rhel9:17708369012026-02-12redhat
redhatdevspaces/udi-rhel9:17701645982026-02-10redhat
redhatoadp/oadp-velero-plugin-rhel9:17686025582026-02-09redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17700554252026-02-05redhat
redhatodf4/rook-ceph-rhel9-operator:17695433022026-02-05redhat
redhatrunc-4:1.2.9-1.rhaos4.16.el82026-02-05redhat
redhatquay/quay-rhel8:17701465652026-02-04redhat
redhatquay/quay-rhel8:17698520132026-02-02redhat
redhatrunc-4:1.2.9-1.rhaos4.17.el92026-01-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/opencontainers/runc—1.4.0-rc.3—
github.com/opencontainers/selinux—1.13.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 10:41 UTCOSV refresh
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 06:30 UTCEPSS rescore
  8. 2026-07-02 17:01 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-24 14:04 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 42 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-19 19:25 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-17 22:35 UTCOSV refresh
  7. 2026-06-17 17:52 UTCEPSS rescore
  8. 2026-06-16 17:52 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-15 17:48 UTCEPSS rescore
  11. 2026-06-14 23:17 UTCEPSS rescore
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:11 UTCEPSS rescore
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-11 14:00 UTCEPSS rescore
  16. 2026-06-10 22:18 UTCEPSS rescore
  17. 2026-06-10 22:18 UTCEPSS rescore
  18. 2026-06-10 13:22 UTCEPSS rescore
  19. 2026-06-10 13:22 UTCEPSS rescore
  20. 2026-06-08 14:16 UTCEPSS rescore
  21. 2026-06-08 14:16 UTCEPSS rescore
  22. 2026-06-07 15:24 UTCEPSS rescore
  23. 2026-06-07 15:24 UTCEPSS rescore
  24. 2026-06-06 13:47 UTCEPSS rescore
  25. 2026-06-06 13:47 UTCEPSS rescore
  26. 2026-06-05 22:46 UTCEPSS rescore
  27. 2026-06-05 22:46 UTCEPSS rescore
  28. 2026-06-05 06:10 UTCEPSS rescore
  29. 2026-06-05 06:10 UTCEPSS rescore
  30. 2026-06-04 13:12 UTCEPSS rescore
  31. 2026-06-04 13:12 UTCEPSS rescore
  32. 2026-06-02 20:12 UTCEPSS rescore
  33. 2026-06-02 20:12 UTCEPSS rescore
  34. 2026-06-01 13:51 UTCEPSS rescore
  35. 2026-06-01 13:51 UTCEPSS rescore
  36. 2026-05-31 22:30 UTCEPSS rescore
  37. 2026-05-31 22:30 UTCEPSS rescore
  38. 2026-05-31 00:16 UTCEPSS rescore
  39. 2026-05-31 00:16 UTCEPSS rescore
  40. 2026-05-29 19:41 UTCEG score recompute
  41. 2026-05-29 19:41 UTCVendor advisory
  42. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCjq6l43d1/proxmox-lxc-docker-fix
    First seen Nov 11, 2025

    Workaround for CVE-2025-52881: Fixes Docker/Podman breakage in Proxmox LXC containers caused by AppArmor incompatibility with runc 1.2.7+. Universal wrapper for community-scripts with automatic AppArmor configuration.

    Open source ↗

Frequently asked(5)

What is CVE-2025-52881?
CVE-2025-52881 is a high vulnerability published on November 6, 2025. 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…
When was CVE-2025-52881 disclosed?
CVE-2025-52881 was first published in the National Vulnerability Database on November 6, 2025, with the most recent update on December 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-52881 actively exploited?
CVE-2025-52881 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-52881?
CVE-2025-52881 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-52881?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-52881, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-52881

Explore →

Is Your Infrastructure Affected by CVE-2025-52881?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs