How severe is CVE-2022-27651?

CVE-2022-27651 has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-27651?

CVE-2022-27651 affects the following packages: github.com/containers/buildah (Go). Ecosystems affected: Go.

How do I fix CVE-2022-27651?

Update github.com/containers/buildah to 1.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-27651 is resolved across your whole dependency graph.

How do I detect CVE-2022-27651 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/buildah, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-27651 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-27651 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-27651 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-27651?

CVE-2022-27651 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-27651?

CVE-2022-27651 is classified as Incorrect Default Permissions (CWE-276). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-27651 published, and has it been updated?

CVE-2022-27651 was published on April 4, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2022-27651 — buildah

MEDIUMFix: containers/buildah@e7e55c9

CVE-2022-27651 is a medium-severity (CVSS 6.8) Incorrect Default Permissions vulnerability in github.com/containers/buildah. A fix is available for github.com/containers/buildah — see the affected versions and patch details below.

Non-empty default inheritable capabilities for linux container in Buildah

Also known asGHSA-c3g4-w6cv-6v7hGO-2022-0417

Published

Apr 4, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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

1 pkg affected

🐹github.com/containers/buildah

Real-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 flaw was found in buildah where containers were incorrectly started with non-empty default permissions. A bug was found in Moby (Docker Engine) where containers were incorrectly started with non-empty inheritable Linux process capabilities, enabling an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. This has the potential to impact confidentiality and integrity.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/containers/buildah`	all versions	1.25.0`go get github.com/containers/buildah@v1.25.0`

Affected Products

3 products · 6 configurations

Application

buildahbuildah_project

< 1.25.0

range

fedorafedoraproject

3 versions

343536

enterprise linuxredhat

2 versions

7.08.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/buildah, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/buildah to 1.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-27651 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.

Red HatModerate

This issue is related to the general vulnerability found in Moby (Docker Engine), which has been assigned CVE-2022-24769. The impact for OpenShift Container Platform is set to LOW as Buildah was shipped but is not being used. No update is planned at this time.

Workaround published by Red Hat

The entry point of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.

Source: Red Hat security advisory for CVE-2022-27651 (CC BY 4.0)

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

O3 Security · Impact-Aware SCA

Is CVE-2022-27651 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works