CVE-2026-40701
Awaiting Analysis
Awaiting Analysis - Queue
BaseFortify
Vulnerability report for CVE-2026-40701, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-05-13
Last updated on: 2026-06-23
Assigner: F5 Networks
Description
Description
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_ssl_module module when the ssl_verify_client directive is set to "on" or "optional," and the ssl_ocsp directive is set to "on" or the leaf parameters are configured with a resolver. With this configuration, an unauthenticated attacker can send requests along with conditions beyond its control that may cause a heap-use-after-free error in the NGINX worker process. This vulnerability may result in limited modification of data or the NGINX worker process restarting.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| f5 | nginx_ingress_controller | From 4.0.0 (inc) to 4.0.1 (inc) |
| f5 | nginx_gateway_fabric | From 1.3.0 (inc) to 1.6.2 (inc) |
| f5 | nginx_gateway_fabric | From 2.0.0 (inc) to 2.6.0 (inc) |
| f5 | nginx_ingress_controller | From 3.5.0 (inc) to 3.7.2 (inc) |
| f5 | nginx_ingress_controller | From 5.0.0 (inc) to 5.4.2 (inc) |
| f5 | nginx_instance_manager | From 2.16.0 (inc) to 2.22.0 (inc) |
| f5 | nginx_plus | From r32 (inc) to r36 (inc) |
| f5 | dos | 4.8.0 |
| f5 | waf | From 5.9.0 (inc) to 5.12.1 (inc) |
| f5 | dos | From 4.3.0 (inc) to 4.7.0 (inc) |
| f5 | waf | From 5.1.0 (inc) to 5.8.0 (inc) |
| f5 | waf | From 4.9.0 (inc) to 4.16.0 (inc) |
| f5 | nginx_open_source | From 1.19.0 (inc) to 1.30.0 (inc) |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
