CVE-2026-65960 · Runtime
NO FIX YET · SEE WHAT TO DO
Tetragon versions before 1.7.0 ship a Helm default that exposes its privileged gRPC API on an unauthenticated TCP listener at localhost:54321. A attacker running or controlling a hostNetwork pod on the same node can call that API to change tracing policies and debug settings, which can lead to privilege escalation or container escape.
first public Jul 27, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Tetragon from the Helm chart before 1.7.0 with the default TCP gRPC listener on Kubernetes nodes. The risk depends on hostNetwork pods sharing a node with Tetragon; deployments that do not expose an unauthenticated TCP listener are not affected.
Not affected if no-hostnetwork-pods, no-tcp-listener, version-1.7.0-or-later
Who cares ebpf, helm, kubernetes, tetragon
helm list -A and the chart values for the gRPC endpoint setting54321 on Kubernetes nodes running TetragonhostNetwork: true pods run on the same nodes as Tetragon1.7.0 or later, which changes the default endpoint to a Unix-domain socketTetragon is an eBPF-based security observability and runtime enforcement project. Versions before 1.7.0 can use a Helm default that exposes the privileged Tetragon gRPC API through an unauthenticated TCP listener on localhost:54321. An attacker who can run or compromise same-node hostNetwork pods can reach the listener and invoke privileged methods without authentication. These methods can add, delete, or reconfigure tracing policies and change debug settings, potentially resulting in privilege escalation or container escape. Version 1.7.0 changes the default endpoint to a Unix-domain socket. Deployments that do not expose an unauthenticated TCP listener are not affected.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.