CVE-2026-65960 json
Tetragon: Unauthenticated Tetragon gRPC admin API accessible from hostNetwork pods
published 2026-11-06 2 d ago modified 2026-11-06 2 d ago also EUVD-2026-118486
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
Tetragon 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.
Patch / fix
- github.com/cilium/tetragon@8e89933 commit
- github.com/cilium/tetragon@fe46101 commit
- github.com/cilium/tetragon#4882 pull request
- github.com/cilium/tetragon/releases/tag/v1.7.0 release
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected products
- cilium tetragon
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
- github.com /cilium/tetragon/pull/4882
- github.com /cilium/tetragon/commit/8e89933d3526f37c04f7523013ff32f8b1c6f62a
- github.com /cilium/tetragon/commit/fe46101770b960ebbf39fe9749bb20d49cf178b2
- github.com /cilium/tetragon/security/advisories/GHSA-6qqg-3qf7-p3v5
- github.com /cilium/tetragon/releases/tag/v1.7.0
Sources
- CVE List CVE-2026-65960
- NVD CVE-2026-65960
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.