NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Default inheritable capabilities for linux container should be emptyGHSA-f3fp-gc8g-vw66

MEDIUMFix: opencontainers/runc@d04de3a

GHSA-f3fp-gc8g-vw66 is a medium-severity (CVSS 5.9) Incorrect Default Permissions vulnerability in github.com/opencontainers/runc. A fix is available for github.com/opencontainers/runc — see the affected versions and patch details below.

Also known asCVE-2022-29162GO-2022-0452
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-f3fp-gc8g-vw66.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk
0.00%0.30%0.60%0.89%0.1%0.4%May 26Sep 26Nov 26

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/opencontainers/runc

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

Impact

A bug was found in runc where runc exec --cap executed processes 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.

Patches

This bug has been fixed in runc 1.1.2. Users should update to this version as soon as possible.

This fix changes runc exec --cap behavior such that the additional capabilities granted to the process being executed (as specified via --cap arguments) do not include inheritable capabilities.

In addition, runc spec is changed to not set any inheritable capabilities in the created example OCI spec (config.json) file.

Credits

The opencontainers project would like to thank Andrew G. Morgan for responsibly disclosing this issue in accordance with the opencontainers org security policy.

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/opencontainers/runcall versions1.1.2go get github.com/opencontainers/runc@v1.1.2

Affected Products

2 products · 4 configurations
OS
fedorafedoraproject
3 versions
343536
Application
runclinuxfoundation
< 1.1.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/opencontainers/runc to 1.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f3fp-gc8g-vw66 is resolved across your whole dependency graph.

  3. 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 HatLow

This issue is rated as low severity as the vulnerability can only result in atypical linux environment,and it's complex exploitation only results in minimal impact on system confidentiality, integrity, and availability in typical environments.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-f3fp-gc8g-vw66 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 8container-tools:rhel8-8070020220929222448.39077419RHSA-2022:7457
Red Hat Enterprise Linux 8container-tools:4.0-8070020220830101436.39077419RHSA-2022:7469
Red Hat Enterprise Linux 9runc-4:1.1.4-1.el9RHSA-2022:8090
Red Hat OpenShift Container Platform 4.11runc-3:1.1.2-1.rhaos4.11.el8RHSA-2022:5068

Frequently Asked Questions

### Impact A bug was found in runc where `runc exec --cap` executed processes 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. ### Patches This bug has been fixed in runc 1.1.2. Users should update to this version as soon as possible. This fix changes `runc exe
O3 Security · Impact-Aware SCA

Is GHSA-f3fp-gc8g-vw66 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Default inheritable capabilities for linux container should…