Syself security assessment
Opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking in go.opentelemetry.io/otel/sdk
Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how GO-2026-5426 affects the ccm, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler components those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.
Syself Kubernetes is not affected by GO-2026-5426 in any of the 10 releases that ship ccm, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler.
Reason: The vulnerable code is not included.
The affected code only runs on non-Linux systems. These programs are built for Linux, so that code is left out and the vulnerable code is not present.
Syself SecurityThe affected code only runs on non-Linux systems. These programs are built for Linux, so that code is left out and the vulnerable code is not present.
Syself SecurityThe affected code only runs on non-Linux systems. These programs are built for Linux, so that code is left out and the vulnerable code is not present.
Syself SecurityThe affected code only runs on non-Linux systems. These programs are built for Linux, so that code is left out and the vulnerable code is not present.
Syself SecurityThe affected code only runs on non-Linux systems. These programs are built for Linux, so that code is left out and the vulnerable code is not present.
Syself SecurityThe affected code only runs on non-Linux systems. These programs are built for Linux, so that code is left out and the vulnerable code is not present.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| ccm v2.0.7 | Not affected | The vulnerable code is not included | — | Details | |
| coredns 1.14.2 | Not affected | The vulnerable code is not included | — | Details | |
| etcd_image 3.6.8-0 | Not affected | The vulnerable code is not included | — | Details | |
| kube_apiserver 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is not included | — | Details | |
| kube_controller_manager 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is not included | — | Details | |
| kube_scheduler 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is not included | — | Details | |
| csi-hcloud v2.21.0, v2.22.1, v2.23.0 | Not affected | The vulnerable code is not included | — | Details |
Scanners such as Trivy and Grype match package versions, so they report GO-2026-5426 whenever the vulnerable version is present, even when it cannot be exploited. Syself publishes its assessments as a VEX (Vulnerability Exploitability eXchange) document for every release. Pass it to your scanner to drop the findings Syself has assessed as not affected or fixed:
trivy image --vex hetzner-apalla-1-36-v10-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v10-advisory.openvex.json Each assessment applies to the package version it names. A finding stays in the report when the document has no assessment for that package, or when the vulnerability is still affected or under investigation.
Download the OpenVEX document for 1.36 v10The severity shown is the upstream rating of the vulnerability itself. The status is Syself's assessment of whether it can be exploited in the components Syself ships, so a critical vulnerability can still be not affected.
Think this assessment is wrong, or found a vulnerability in Syself? Contact us.