Skip to main content
CVE-2025-52881VulnerabilityPublished Updated

SUSE · Security update for buildah

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2025-52881· High 7.3

Not known to be exploited · CVSS 7.3 High.

Data as of 16 Nov 2026, 00:18 UTC

CVSS 4.0 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubopencontainers/runcpkg:github/opencontainers/runcOther threatsAffected
  • =1.2.7
  • =1.3.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update for buildah has been released that fixes the container breakout vulnerability. Users should apply this update promptly to mitigate the risk. No additional mitigation steps are indicated.

Description

A security update for buildah addresses a vulnerability (CVE-2025-52881) that allowed container breakouts by bypassing runc's restrictions on writing to arbitrary /proc files. This issue could enable an attacker to escape container isolation. The update also fixes warnings encountered when using podman and buildah with runc 1.3.2 in rootless mode.

References

Community reviews

Loading reviews…