Skip to main content

Syself security assessment

GO-2026-4918 in Syself Kubernetes

Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

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

Reason: An attacker cannot reach the vulnerable code.

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

ccm v2.0.7
Not affected Unknown
An attacker cannot reach the vulnerable code

This flaw can hang a program only when it connects out to a malicious server. The affected components connect only to trusted internal services, so no attacker-run server is reached.

Syself Security
coredns 1.14.2
Not affected Unknown
An attacker cannot reach the vulnerable code

This flaw can hang a program only when it connects out to a malicious server. The affected parts connect only to trusted internal services, never to servers a tenant controls, so the flaw cannot be triggered.

Syself Security
etcd_image 3.6.8-0
Not affected Unknown
An attacker cannot reach the vulnerable code

This flaw lets a harmful server make a program that connects to it stop responding. The affected parts connect only to trusted internal services, never to a server an attacker controls, so they cannot be made to stop responding.

Syself Security
metrics-server 1.8.24
Not affected Unknown
An attacker cannot reach the vulnerable code

This flaw can hang a program only when it connects out to a malicious server. The affected components connect only to trusted internal services, so no attacker-run server is reached.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
ccm v2.0.7Not affectedAn attacker cannot reach the vulnerable code—Details
coredns 1.14.2Not affectedAn attacker cannot reach the vulnerable code—Details
etcd_image 3.6.8-0Not affectedAn attacker cannot reach the vulnerable code—Details
metrics-server 1.8.23, 1.8.24Not affectedAn attacker cannot reach the vulnerable code—Details
cluster-proportional-autoscaler v1.10.3Not affectedAn attacker cannot reach the vulnerable code—Details
cilium 1.20.0Not affectedAn attacker cannot reach the vulnerable code—Details
cilium_envoy v1.37.5-1782911245-7cffc778c923f68a77954a53b1a98d6b5353f004Not affectedAn attacker cannot reach the vulnerable code—Details
csi-hcloud v2.21.0Not affectedAn attacker cannot reach the vulnerable code—Details
kube_apiserver 1.36.3Not affectedAn attacker cannot reach the vulnerable code—Details
kube_controller_manager 1.36.3Not affectedAn attacker cannot reach the vulnerable code—Details
kube_scheduler 1.36.3Not affectedAn attacker cannot reach the vulnerable code—Details

Frequently asked questions

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

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