Skip to main content

Syself security assessment

GO-2026-5970 in Syself Kubernetes

Infinite loop on invalid input in golang.org/x/text

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-5970 affects the ccm, cilium, cilium_envoy, cilium_operator, cluster-proportional-autoscaler, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server, nvidia-device-plugin components those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.

Not affected in 1.36 v10 Upstream severity: Unknown Last assessed

Syself Kubernetes is not affected by GO-2026-5970 in any of the 10 releases that ship ccm, cilium, cilium_envoy, cilium_operator, cluster-proportional-autoscaler, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server, nvidia-device-plugin.

Reason: The vulnerable code is never executed.

Our assessment in 1.36 v10, the newest release with this finding

ccm v2.0.7
Not affected Unknown
The vulnerable code is never executed

This flaw needs the text-cleanup code to run over broken text supplied by an attacker. These components never do that, so the affected code is not reached.

Syself Security
The vulnerable code is never executed

These components do not run the affected text-normalization function over untrusted, invalid text, so the loop that never ends cannot be triggered.

Syself Security
coredns 1.14.2
Not affected Unknown
The vulnerable code is never executed

The flaw only occurs when a specific text-normalization routine runs over malformed text. The components here do not run that routine on untrusted text, so the flaw is never reached.

Syself Security
etcd_image 3.6.8-0
Not affected Unknown
The vulnerable code is never executed

This flaw can make text handling loop forever, but only when a program feeds it broken text through one specific function. These components do not use that function on untrusted text.

Syself Security
metrics-server 1.8.24
Not affected Unknown
The vulnerable code is never executed

This flaw needs the text-cleanup code to run over broken text supplied by an attacker. These components never do that, so the affected code is not reached.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
ccm v2.0.7Not affectedThe vulnerable code is never executed—Details
cluster-proportional-autoscaler v1.10.3, v1.11.0Not affectedThe vulnerable code is never executed—Details
coredns 1.14.2Not affectedThe vulnerable code is never executed—Details
etcd_image 3.6.8-0Not affectedThe vulnerable code is never executed—Details
metrics-server 1.8.23, 1.8.24Not affectedThe vulnerable code is never executed—Details
csi-hcloud v2.21.0, v2.22.1, v2.23.0Not affectedThe vulnerable code is never executed—Details
cilium 1.20.0, 1.20.1Not affectedThe vulnerable code is never executed—Details
cilium_envoy v1.37.5-1782911245-7cffc778c923f68a77954a53b1a98d6b5353f004, v1.37.5-1786810558-766ccfb37260a43e9d228837aa84ce3faf9f64e7Not affectedThe vulnerable code is never executed—Details
cilium_operator 1.20.0, 1.20.1Not affectedThe vulnerable code is never executed—Details
kube_apiserver 1.36.3Not affectedThe vulnerable code is never executed—Details
kube_controller_manager 1.36.3Not affectedThe vulnerable code is never executed—Details
kube_scheduler 1.36.3Not affectedThe vulnerable code is never executed—Details
nvidia-device-plugin v0.19.3Not affectedThe vulnerable code is never executed—Details

Frequently asked questions

My scanner reports GO-2026-5970 in a Syself cluster. What should I do?

Scanners such as Trivy and Grype match package versions, so they report GO-2026-5970 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 v10

What do the statuses mean?

Not affected
The component ships in the release, but Syself has assessed that the vulnerability cannot be exploited there. The reason column says why.
Fixed
The release ships a version of the component that carries the fix.
Affected
The vulnerability can affect the release. Upgrade to a release listed as fixed once one is available.
Under Investigation
Syself is still assessing whether the vulnerability affects the release.

Why can the severity differ from other sources?

The 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.

References

Think this assessment is wrong, or found a vulnerability in Syself? Contact us.