CVE-2026-40701: NGINX ngx_http_ssl_module vulnerability

Published May 13, 2026
·
Updated

Last updated 6 June 2026

Other sources

NGINX Plus and NGINX Open Source have a vulnerability in the ngxhttpsslmodule module when the sslverifyclient directive is set to "on" or "optional," and the sslocsp 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.

Launchpad

Affected Software

17 affected componentsFixes available
F5 NGINX Plus
Nginx NGINX Open Source
Microsoft azl3 nginx 1.28.3-1
debian/nginx<=1.18.0-6.1+deb11u3, <=1.22.1-9+deb12u6, <=1.26.3-3+deb13u4
1.18.0-6.1+deb11u61.22.1-9+deb12u71.26.3-3+deb13u51.30.1-3
F5 Dos Nginx>=4.3.0<=4.7.0
F5 Dos Nginx=4.8.0
F5 NGINX Gateway Fabric>=1.3.0<=1.6.2
F5 NGINX Gateway Fabric>=2.0.0<=2.6.0
F5 NGINX Ingress Controller>=3.5.0<=3.7.2
F5 NGINX Ingress Controller>=4.0.0<=4.0.1
F5 NGINX Ingress Controller>=5.0.0<=5.4.2
F5 NGINX Instance Manager>=2.16.0<=2.22.0
F5 NGINX Open Source>=1.19.0<=1.30.0
F5 NGINX Plus>=r32<=r36
F5 Waf Nginx>=4.9.0<=4.16.0
F5 Waf Nginx>=5.1.0<=5.8.0
F5 Waf Nginx>=5.9.0<=5.12.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.18.0-6.1+deb11u6Fixed in 1.22.1-9+deb12u7Fixed in 1.26.3-3+deb13u5Fixed in 1.30.1-3
  2. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.18.0-6.1+deb11u6
  3. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.22.1-9+deb12u7
  4. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.26.3-3+deb13u5
  5. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.30.1-3
  6. Configuration

    Set ssl_verify_client to 'off' (avoid using 'on' or 'optional') in the server/location block to prevent the vulnerable configuration described.

    NGINX ngx_http_ssl_module ssl_verify_client = off
  7. Configuration

    Set ssl_ocsp to 'off' and do not configure leaf OCSP parameters with a resolver (avoid enabling ssl_ocsp or leaf parameters with a resolver) to eliminate the vulnerable condition.

    NGINX ngx_http_ssl_module ssl_ocsp = off

Event History

May 13, 2026
CVE Published
via MITRE·02:12 PM
Data Sourced
via MITRE·02:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
Affected Software
May 16, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
Jun 1, 2026
Data Sourced
via Debian·06:32 PM
DescriptionAffected Software
Data Sourced
via Launchpad·06:33 PM
Description
Jun 6, 2026
Data Sourced
via Ubuntu·06:36 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40701?

CVE-2026-40701 has been assigned a high severity rating due to the potential for attackers to exploit it for unauthorized access.

2

How do I fix CVE-2026-40701?

To mitigate CVE-2026-40701, disable the ssl_verify_client directive or ensure that the ssl_ocsp directive is appropriately configured.

3

Which versions of NGINX are affected by CVE-2026-40701?

CVE-2026-40701 affects both NGINX Plus and NGINX Open Source when specific SSL configuration settings are applied.

4

What is the impact of CVE-2026-40701?

The impact of CVE-2026-40701 includes potential exposure of sensitive information and increased risk of security breaches.

5

Is there a workaround for CVE-2026-40701?

A temporary workaround for CVE-2026-40701 is to modify the SSL settings to disable client certificate verification as a risk mitigation measure.

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