<Vulnerability name="CVE-2026-40701">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Moderate</ThreatSeverity>
    <PublicDate>2026-05-13T14:12:43</PublicDate>
    <Bugzilla id="2477076" url="https://bugzilla.redhat.com/show_bug.cgi?id=2477076" xml:lang="en:us">
nginx: ngx_http_ssl_module: data corruption and denial of service
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>4.8</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-416</CWE>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in the ngx_http_ssl_module module of NGINX. When the ssl_verify_client directive is set to "on" or "optional" and the ssl_ocsp directive is enabled or its leaf parameters are configured with a resolver, an unauthenticated attacker can send crafted requests to cause a use-after-free issue in the worker process, resulting in a limited modification of memory data or a denial of service by forcing the process to restart.
    </Details>
    <Statement xml:lang="en:us">
To exploit this flaw, the ssl_verify_client directive must be set to "on" or "optional" and the ssl_ocsp directive must be enabled or its leaf parameters configured with a resolver, limiting its exposure as this is not the default configuration. This issue allows an attacker to have limited control to modify memory data from the worker process or cause a denial of service by forcing the process to restart, but it cannot cause a complete system denial of service. Due to these reasons, this flaw has been rated with a moderate severity.
    </Statement>
    <Mitigation xml:lang="en:us">
To mitigate this issue, specifically set the OCSP responder using the ssl_ocsp_responder directive or switch from live OCSP validation to static CRL files using the ssl_crl directive. If neither configuration is possible, using a local DNS server to cache and quickly resolve OCSP responder names can reduce the probability of exploitation.
    </Mitigation>
    <PackageState cpe="cpe:/o:redhat:enterprise_linux:10">
        <ProductName>Red Hat Enterprise Linux 10</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>nginx</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/o:redhat:enterprise_linux:8">
        <ProductName>Red Hat Enterprise Linux 8</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>nginx:1.24/nginx</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/o:redhat:enterprise_linux:9">
        <ProductName>Red Hat Enterprise Linux 9</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>nginx</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/o:redhat:enterprise_linux:9">
        <ProductName>Red Hat Enterprise Linux 9</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>nginx:1.24/nginx</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/o:redhat:enterprise_linux:9">
        <ProductName>Red Hat Enterprise Linux 9</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>nginx:1.26/nginx</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:hummingbird:1">
        <ProductName>Red Hat Hardened Images</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>nginx</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:insights_proxy:1">
        <ProductName>Red Hat Lightspeed proxy 1</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>insights-proxy/insights-proxy-container-rhel9</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-40701
https://nvd.nist.gov/vuln/detail/CVE-2026-40701
https://my.f5.com/manage/s/article/K000161021
    </References>
</Vulnerability>