Skip to main content

Syself security assessment

GO-2026-6348 in Syself Kubernetes

Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation in google.golang.org/grpc

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-6348 affects the ccm, cilium, cilium_envoy, cilium_operator, 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-6348 in any of the 10 releases that ship ccm, cilium, cilium_envoy, cilium_operator, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server, nvidia-device-plugin.

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 denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

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

This denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

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

This denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

Syself Security
kube_apiserver 1.36.6
Not affected Unknown
An attacker cannot reach the vulnerable code

This denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

Syself Security
kube_controller_manager 1.36.6
Not affected Unknown
An attacker cannot reach the vulnerable code

This denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

Syself Security
kube_scheduler 1.36.6
Not affected Unknown
An attacker cannot reach the vulnerable code

This denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

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

This denial-of-service needs a malicious peer opening HTTP/2 streams to an exposed gRPC server. These components reach gRPC only over local file sockets or as clients, and the one network endpoint requires mutual certificate authentication.

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
kube_apiserver 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedAn attacker cannot reach the vulnerable code—Details
kube_controller_manager 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedAn attacker cannot reach the vulnerable code—Details
kube_scheduler 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedAn attacker cannot reach the vulnerable code—Details
metrics-server 1.8.23, 1.8.24Not affectedAn attacker cannot reach the vulnerable code—Details
csi-hcloud v2.21.0, v2.22.1, v2.23.0Not affectedAn attacker cannot reach the vulnerable code—Details
cilium 1.20.0, 1.20.1Not affectedAn attacker cannot reach the vulnerable code—Details
cilium_envoy v1.37.5-1782911245-7cffc778c923f68a77954a53b1a98d6b5353f004, v1.37.5-1786810558-766ccfb37260a43e9d228837aa84ce3faf9f64e7Not affectedAn attacker cannot reach the vulnerable code—Details
cilium_operator 1.20.0, 1.20.1Not affectedAn attacker cannot reach the vulnerable code—Details
nvidia-device-plugin v0.19.3Not affectedAn attacker cannot reach the vulnerable code—Details

Frequently asked questions

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

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