CVE-2026-96615: NGINX Gateway Fabric vulnerability

Published Oct 14, 2026
·
Updated

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.

Other sources

NGINX Gateway Fabric has a vulnerability when it is configured with Gateway Custom Resource Definition (CRD) and has 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 Transport Layer Security (TLS) private keys of Gateway deployments in another namespace.

— F5

Affected Software

2 affected componentsFixes available
F5 NGINX Gateway Fabric
F5 NGINX Gateway Fabric>=2.0.0<=2.7.2
2.8.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.8.0

Event History

Oct 14, 2026
Advisory Published
via F5·01:39 PM
Data Sourced
via F5·01:39 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·02:40 PM
Data Sourced
via MITRE·02:40 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments of NGINX Gateway Fabric configured with the Gateway CRD and using an authenticated gRPC connection with NGINX Agent are exposed. The impact is limited to the control plane; no data plane exposure is described.

2

What access does an attacker need?

An attacker needs to be authenticated, namespaced, and have access to a service account. With that access, they may impersonate the authenticated NGINX Agent gRPC connection.

3

What could an attacker obtain?

An attacker may be able to read TLS private keys belonging to Gateway deployments in another namespace. The described impact is confidentiality-only.

4

Are end-of-technical-support versions covered by the evaluation?

No. Software versions that have reached End of Technical Support are not evaluated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203