CVE-2022-27651Medium· 6.8▾ SunlitNon-empty default inheritable capabilities for linux container in Buildah
▾ Sunlit zone — Low / medium · no exploitation signal
impact 37.4 · likelihood 0.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 1.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.2%
1.2% → 1.3%
A bug was found in Buildah where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
github.com/containers/buildah < 1.25.0Upgrade to a patched release:
github.com/containers/buildah 1.25.0Connected by shared product, vendor, weakness, or advisory.
CVE-2021-3602Medium· 5.5Buildah processes using chroot isolation may leak environment values to intermediate processes
CVE-2024-11218High· 8.6A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile
CVE-2026-44517Medium· 6.3Buildah is a tool that facilitates building OCI images
CVE-2022-1227High· 8.8Podman publishes a malicious image to public registries
CVE-2022-27649High· 7.5Podman's default inheritable capabilities for linux container not empty
CVE-2025-6032High· 8.3A flaw was found in Podman