VULNpocalypse

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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2025-11-06).

Weakness: CWE-61: UNIX Symbolic Link (Symlink) Following; CWE-363: Race Condition Enabling Link Following

How it can be exploited

Exploitable with local access with low attack complexity only when specific conditions are present needing low privileges and a user must actively take an action. Impact: confidentiality high, integrity high, availability high. 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

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-14040, CNNVD-202511-488, EUVD-2025-37940, GHSA-9493-h29p-rfm2, GHSA-cgrx-mc8f-2prm, GHSA-qw9x-cqr3-wc7r, GHSA-wwrx-w7c9-rf87

VEDAS cluster: VEDAS:BEASTVISION

Exploit Observer has no public exploit code that names this CVE or one of its aliases.

Vulnerability databases and vendor advisories (17)

Catalogue entries, not exploit evidence.

224 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.008
low predicted chance of attack
VEDAS
0.825
some exploit evidence
On CISA KEV
Not listed
Detection rule
Out of scope (local)

Who is affected

ProductAffectedNot affected
opencontainers runcversion <= 1.2.7, < 1.2.8
version <= 1.3.2, < 1.3.3
version <= 1.4.0-rc.2, < 1.4.0-rc.3		Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: linuxfoundation runc, ао_«нтц_ит_роса» роса_хром, ооо_«ред_софт» ред_ос, ооо_«русбитех-астра» платформа_контейнеризации_«боцман», сообщество_свободного_программного_обеспечения runc.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

Advisories on this CVE

References

Other references

8 more

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.