Skip to main content

Syself security assessment

CVE-2026-40228 in Syself Kubernetes

In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWa…

Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how CVE-2026-40228 affects the systemd 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 CVE-2026-40228 in any of the 10 releases that ship systemd.

Reason: An attacker cannot reach the vulnerable code.

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

systemd 257.13
Not affected Unknown
An attacker cannot reach the vulnerable code

Triggering this needs an untrusted local user to send an emergency log message. The node has no such users, so the affected message-forwarding code cannot be driven by an attacker.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
systemd 257.13Not affectedAn attacker cannot reach the vulnerable code—Details

Frequently asked questions

My scanner reports CVE-2026-40228 in a Syself cluster. What should I do?

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