Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.1
CVE-2026-96615: NGINX Gateway Fabric allows cross-namespace TLS key theft
CVE-2026-96615 · published 14 days ago
Summary
If NGINX Gateway Fabric is set up with a specific custom resource and an authenticated gRPC link to the NGINX Agent, a user who has a service‑account token in one namespace can pretend to be the Agent and read the TLS private keys used by gateways in other namespaces. This could let an attacker decrypt traffic or impersonate those services. Restrict access to the gRPC connection and review service‑account permissions to prevent the misuse.
What to do
- Update nginx-gateway-fabric to version 2.8.0.
- Update f5 nginx gateway fabric to version 2.8.0 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | f5 | nginx gateway fabric | < 2.8.0 |
| Bitnami | – | nginx-gateway-fabric |
>= 2.0.0, < 2.8.0 Fix: upgrade to 2.8.0
|
Original advisory text
NGINX Gateway Fabric vulnerability
Description
NGINX Gateway Fabric has a vulnerability when it is configured with Gateway
Custom Resource Definition (CRD) and have an authenticated gRPC connection with NGINX Agent. A namespaced
authenticated attacker with access to a service account may impersonate the authenticated NGINX Agent gRPC connection to read TLS private keys of Gateway deployments in another namespace.
Impact
A remote authenticated attacker may be able to read TLS private keys of Gateway deployments in another namespace.
There is no data plane exposure; this is a control plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
NGINX Gateway Fabric has a vulnerability when it is configured with Gateway
Custom Resource Definition (CRD) and have an authenticated gRPC connection with NGINX Agent. A namespaced
authenticated attacker with access to a service account may impersonate the authenticated NGINX Agent gRPC connection to read TLS private keys of Gateway deployments in another namespace.
Impact
A remote authenticated attacker may be able to read TLS private keys of Gateway deployments in another namespace.
There is no data plane exposure; this is a control plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Severity
7.1
High
Type
CWE-290Authentication Bypass by Spoofing
Timeline
Published21 Oct 2026
Updated4 Nov 2026
First seen14 Oct 2026
Track software like this
Free during beta