Syself security assessment
Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog
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-6179 affects the coredns, nvidia-device-plugin 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-6179 in any of the 10 releases that ship coredns, nvidia-device-plugin.
Reason: The vulnerable code is never executed.
The affected transparency-log verification is used only by the build toolchain when fetching modules. The running service does not verify such logs, so the vulnerable code never executes.
Syself SecurityScanners such as Trivy and Grype match package versions, so they report GO-2026-6179 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.