CVE-2022-27649 is a high-severity (CVSS 7.5) Incorrect Default Permissions vulnerability in github.com/containers/podman/v4. A fix is available for github.com/containers/podman/v4 — see the affected versions and patch details below.
Podman's default inheritable capabilities for linux container not empty
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/containers/podman/v4Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A bug was found in Podman 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/containers/podman/v4 | all versions | 4.0.3go get github.com/containers/podman/v4@v4.0.3 |
Affected Products
fedorafedoraprojectpodmanpodman_projectdeveloper toolsredhatenterprise linuxredhatenterprise linux eusredhatenterprise linux for ibm z systemsredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/podman/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/podman/v4 to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-27649 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This issue is related to the general vulnerability found in Moby (Docker Engine), which has been assigned CVE-2022-24769.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | container-tools:3.0-8050020220411083214.e34216c9 | RHSA-2022:1565 |
| Red Hat Enterprise Linux 8 | container-tools:2.0-8050020220411114323.e34216c9 | RHSA-2022:1566 |
| Red Hat Enterprise Linux 8 | container-tools:rhel8-8060020220401155929.2e213529 | RHSA-2022:1762 |
| Red Hat Enterprise Linux 8.2 Extended Update Support | container-tools:2.0-8020020220420173758.28c38760 | RHSA-2022:4651 |
| Red Hat Enterprise Linux 8.4 Extended Update Support | container-tools:2.0-8040020220411112506.c0c392d5 | RHSA-2022:1407 |
| Red Hat Enterprise Linux 8.4 Extended Update Support | container-tools:3.0-8040020220419093313.c0c392d5 | RHSA-2022:4816 |
Frequently Asked Questions
Is CVE-2022-27649 in your dependencies?
Find it across Go, including transitive dependencies.