Syself security assessment
OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs in go.opentelemetry.io/otel/exporters/otlp/otlptrace
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-6505 affects the ccm, 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.
Syself Kubernetes is not affected by GO-2026-6505 in any of the 10 releases that ship ccm, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server.
Reason: The vulnerable code is never executed.
This flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself SecurityThis flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself SecurityThis flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself SecurityThis flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself SecurityThis flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself SecurityThis flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself SecurityThis flaw only writes a configured telemetry endpoint address into local logs, and only when telemetry export is enabled. It exposes no attacker-controlled data and is not reachable from the network.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| ccm v2.0.7 | Not affected | The vulnerable code is never executed | — | Details | |
| coredns 1.14.2 | Not affected | The vulnerable code is never executed | — | Details | |
| etcd_image 3.6.8-0 | Not affected | The vulnerable code is never executed | — | Details | |
| kube_apiserver 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is never executed | — | Details | |
| kube_controller_manager 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is never executed | — | Details | |
| kube_scheduler 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is never executed | — | Details | |
| metrics-server 1.8.23, 1.8.24 | Not affected | The vulnerable code is never executed | — | Details | |
| csi-hcloud v2.21.0, v2.22.1, v2.23.0 | Not affected | The vulnerable code is never executed | — | Details |
Scanners such as Trivy and Grype match package versions, so they report GO-2026-6505 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 v10The 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.
Think this assessment is wrong, or found a vulnerability in Syself? Contact us.