Skip to main content

Syself security assessment

GO-2026-5841 in Syself Kubernetes

OOB read in github.com/klauspost/compress/s2

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-5841 affects the cilium, cilium_operator, coredns, etcd_image, 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-5841 in any of the 10 releases that ship cilium, cilium_operator, coredns, etcd_image, metrics-server.

Reason: An attacker cannot reach the vulnerable code.

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

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

This flaw makes the compression library read past the end of memory, but only when an attacker controls the special dictionary used to compress. These components never expose that input.

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

The out-of-range memory read needs the s2 compressor to run with a data dictionary chosen by an attacker. These components never use attacker-supplied dictionaries, so it cannot happen.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
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
cilium 1.20.0, 1.20.1, 1.20.2Not affectedAn attacker cannot reach the vulnerable code—Details
cilium_operator 1.20.0, 1.20.1, 1.20.2Not affectedAn attacker cannot reach the vulnerable code—Details
metrics-server 1.8.23Not affectedAn attacker cannot reach the vulnerable code—Details

Frequently asked questions

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

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