Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Link Following in Kata RuntimeGHSA-877x-32pm-p28x

HIGHFix: kata-containers/runtime#2713

GHSA-877x-32pm-p28x is a high-severity (CVSS 8.8) CWE-59 vulnerability in github.com/kata-containers/runtime. A fix is available for github.com/kata-containers/runtime — see the affected versions and patch details below.

Also known asCVE-2020-2026
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk
0.00%0.33%0.65%0.97%0.3%0.5%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-877x-32pm-p28x by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
🐹github.com/kata-containers/runtime🐹github.com/kata-containers/runtime🐹github.com/kata-containers/runtime

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 malicious guest compromised before a container creation (e.g. a malicious guest image or a guest running multiple containers) can trick the kata runtime into mounting the untrusted container filesystem on any host path, potentially allowing for code execution on the host. This issue affects: Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; Kata Containers 1.9 and earlier versions.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kata-containers/runtimeall versions1.9.1go get github.com/kata-containers/runtime@v1.9.1
🐹Gogithub.com/kata-containers/runtime≥ 1.10.0&&< 1.10.61.10.6go get github.com/kata-containers/runtime@v1.10.6
🐹Gogithub.com/kata-containers/runtime≥ 1.11.0&&< 1.11.11.11.1go get github.com/kata-containers/runtime@v1.11.1

Affected Products

2 products · 4 configurations
OS
fedorafedoraproject
1 version
31
Application
runtimekatacontainers
≥ 1.11 && ≤ 1.9
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/kata-containers/runtime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/kata-containers/runtime to 1.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-877x-32pm-p28x is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

A malicious guest compromised before a container creation (e.g. a malicious guest image or a guest running multiple containers) can trick the kata runtime into mounting the untrusted container filesystem on any host path, potentially allowing for code execution on the host. This issue affects Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; Kata Containers 1.9 and earlier versions.
O3 Security · Impact-Aware SCA

Is GHSA-877x-32pm-p28x in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Link Following in Kata Runtime (High 8.8)