Skip to main content

Syself security assessment

GO-2026-5024 in Syself Kubernetes

Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows

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-5024 affects the ccm, cilium, cilium_operator, cluster-proportional-autoscaler, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, kubegate, metrics-server 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-5024 in any of the 10 releases that ship ccm, cilium, cilium_operator, cluster-proportional-autoscaler, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, kubegate, metrics-server.

Reason: The vulnerable code is not included.

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

ccm v2.0.7
Not affected Unknown
The vulnerable code is not included

The affected code only runs on Windows. These programs are built for Linux, so that code is not included in them and cannot run.

Syself Security
cilium 1.20.4
Not affected Unknown
The vulnerable code is not included

The affected code only builds for Windows. These programs are built for Linux, so that code is not included and the vulnerable code is not present.

Syself Security
cilium 1.20.4
Not affected Unknown
The vulnerable code is not included

The affected code is part of the library that only builds on Windows. These Linux programs do not include it, so it is not present.

Syself Security
cilium_operator 1.20.4
Not affected Unknown
The vulnerable code is not included

The affected code only builds for Windows. These programs are built for Linux, so that code is not included and the vulnerable code is not present.

Syself Security
coredns 1.14.2
Not affected Unknown
The vulnerable code is not included

The affected code only builds for Windows. These programs are built for Linux, so that code is not included and the vulnerable code is not present.

Syself Security
etcd_image 3.6.8-0
Not affected Unknown
The vulnerable code is not included

The flawed code is only for Windows systems. These programs are built for Linux, so that code is not included.

Syself Security
metrics-server 1.8.24
Not affected Unknown
The vulnerable code is not included

The affected code only runs on Windows. These programs are built for Linux, so that code is not included in them and cannot run.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
ccm v2.0.7Not affectedThe vulnerable code is not included—Details
cilium 1.20.0, 1.20.1, 1.20.2, 1.20.4Not affectedThe vulnerable code is not included—Details
cilium_operator 1.20.0, 1.20.1, 1.20.2, 1.20.4Not affectedThe vulnerable code is not included—Details
coredns 1.14.2Not affectedThe vulnerable code is not included—Details
etcd_image 3.6.8-0Not affectedThe vulnerable code is not included—Details
metrics-server 1.8.23, 1.8.24Not affectedThe vulnerable code is not included—Details
cluster-proportional-autoscaler v1.10.3Not affectedThe vulnerable code is not included—Details
kubegate v0.0.5, v0.0.7Not affectedThe vulnerable code is not included—Details
csi-hcloud v2.21.0Not affectedThe vulnerable code is not included—Details
kube_apiserver 1.36.3Not affectedThe vulnerable code is not included—Details
kube_controller_manager 1.36.3Not affectedThe vulnerable code is not included—Details
kube_scheduler 1.36.3Not affectedThe vulnerable code is not included—Details

Frequently asked questions

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

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