Skip to main content

Syself security assessment

GO-2025-3521 in Syself Kubernetes

Kubernetes GitRepo Volume Inadvertent Local Repository Access in k8s.io/kubernetes

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-2025-3521 affects the kubernetes component 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-2025-3521 in any of the 10 releases that ship kubernetes.

Reason: The vulnerable code is never executed.

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

kubernetes 1.36.6
Not affected Unknown
The vulnerable code is never executed

The affected feature is a built-in Git-based storage volume that is turned off by default and is not enabled on the node, so the affected code never runs.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
kubernetes 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedThe vulnerable code is never executed—Details

Frequently asked questions

My scanner reports GO-2025-3521 in a Syself cluster. What should I do?

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