Is CVE-2026-65960 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-65960 being exploited in the wild.

How severe is CVE-2026-65960?

High severity, with a CVSS score of 8.8, published 6 November 2026.

Is there a fix for CVE-2026-65960?

Yes: fixed in 1.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-65960 attacked?

It is attacked over the network or from the adjacent network, in a hosted service.

Am I affected by CVE-2026-65960?

Check whether you run Cilium Tetragon at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-65960: Cilium Tetragon gRPC API unauthenticated access

CVE-2026-65960 · Severity: high · CVSS 8.8 · Published 2026-11-06

Tetragon is a security observability tool that monitors and enforces container security policies using eBPF. Versions before 1.7.0 expose its privileged gRPC API over an unauthenticated TCP port, allowing attackers in the same Kubernetes node to invoke administrative methods like modifying security policies or enabling debug modes without authentication, potentially enabling privilege escalation or container escape.

Vendors: Cilium.

Quick answers

Is CVE-2026-65960 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-65960 being exploited in the wild.
How severe is CVE-2026-65960?: High severity, with a CVSS score of 8.8, published 6 November 2026.
Which products and versions are affected?: Cilium Tetragon before 1.7.0.
Is there a fix for CVE-2026-65960?: Yes: fixed in 1.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65960 attacked?: It is attacked over the network or from the adjacent network, in a hosted service.
Am I affected by CVE-2026-65960?: Check whether you run Cilium Tetragon at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.7.0

Technical details

The vulnerability stems from a Helm default configuration that exposes the Tetragon gRPC API via an unauthenticated TCP listener on localhost:54321 in versions before 1.7.0. Attackers with the ability to run or compromise hostNetwork pods on the same node can reach this listener and invoke privileged gRPC methods without authentication to add, delete, or reconfigure tracing policies and modify debug settings. The fix in version 1.7.0 changes the default endpoint to a Unix-domain socket, restricting access to processes on the same host with appropriate filesystem permissions.

Affected products

Cilium Tetragon before 1.7.0

Timeline

2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.