GHSA-g5p6-327m-3fxx — talos
HIGHGHSA-g5p6-327m-3fxx is a high-severity (CVSS 8.6) vulnerability in github.com/siderolabs/talos. A fix is available for github.com/siderolabs/talos — see the affected versions and patch details below.
Talos Linux ships runc vulnerable to the escape to the host attack
Real-World Exposure
github.com/siderolabs/talos🐹github.com/siderolabs/talosReal-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
Snyk has discovered a vulnerability in all versions of runc <=1.1.11, as used by the Docker engine, along with other containerization technologies such as Kubernetes. Exploitation of this issue can result in container escape to the underlying host OS, either through executing a malicious image or building an image using a malicious Dockerfile or upstream image (i.e., when using FROM). This issue has been assigned the CVE-2024-21626.
Patches
runc runtime was updated to 1.1.12 in Talos v1.5.6 and v1.6.4.
Workarounds
Inspect the workloads running on the cluster to make sure they are not trying to exploit the vulnerability.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/siderolabs/talos | ≥ 1.6.0&&< 1.6.4 | 1.6.4go get github.com/siderolabs/talos@v1.6.4 |
| 🐹Go | github.com/siderolabs/talos | all versions | 1.5.6go get github.com/siderolabs/talos@v1.5.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/siderolabs/talos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/siderolabs/talos to 1.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5p6-327m-3fxx is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g5p6-327m-3fxx can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g5p6-327m-3fxx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g5p6-327m-3fxx in your dependencies?
O3 Security finds GHSA-g5p6-327m-3fxx across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.