OESA-2026-2511 (CVE-2026-40701)
Vulnerability from osv_openeuler – Published: 2026-05-29 11:11 – Updated: 2026-08-06 11:11 – Source websiteNGINX is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server.
Security Fix(es):
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.(CVE-2026-40701)
NGINX Open Source have a vulnerability in the ngx_http_charset_module module. When charset, source_charset, and charset_map and proxy_pass with disabled buffering ("off") directives are configured, unauthenticated attackers can send requests that with conditions beyond the attackers' control to cause a heap buffer over-read in the NGINX worker process, leading to limited disclosure of memory or a restart. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.(CVE-2026-42934)
A vulnerability exists in the ngx_http_scgi_module and ngx_http_uwsgi_module modules that may result in excessive memory allocation or an over-read of data. When scgi_pass or uwsgi_pass is configured, an unauthenticated attacker with man-in-the-middle (MITM) ability to control responses from an upstream server may be able to read the memory of the NGINX worker process or restart it. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.(CVE-2026-42946)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"nginx-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-debuginfo-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-debugsource-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-mod-devel-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-mod-http-image-filter-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-mod-http-perl-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-mod-http-xslt-filter-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-mod-mail-1.24.0-10.oe2403sp3.aarch64.rpm",
"nginx-mod-stream-1.24.0-10.oe2403sp3.aarch64.rpm"
],
"noarch": [
"nginx-all-modules-1.24.0-10.oe2403sp3.noarch.rpm",
"nginx-filesystem-1.24.0-10.oe2403sp3.noarch.rpm",
"nginx-help-1.24.0-10.oe2403sp3.noarch.rpm"
],
"src": [
"nginx-1.24.0-10.oe2403sp3.src.rpm"
],
"x86_64": [
"nginx-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-debuginfo-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-debugsource-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-mod-devel-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-mod-http-image-filter-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-mod-http-perl-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-mod-http-xslt-filter-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-mod-mail-1.24.0-10.oe2403sp3.x86_64.rpm",
"nginx-mod-stream-1.24.0-10.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "nginx",
"purl": "pkg:rpm/openEuler/nginx\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.24.0-10.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "NGINX is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server.\r\n\r\nSecurity Fix(es):\n\nNGINX Open Source have a vulnerability in the ngx_http_ssl_module\u00a0module when the ssl_verify_client\u00a0directive is set to \u0026quot;on\u0026quot; or \u0026quot;optional,\u0026quot; and the ssl_ocsp\u00a0directive is set to \u0026quot;on\u0026quot; or the leaf\u00a0parameters 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.\u00a0Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.(CVE-2026-40701)\n\nNGINX Open Source have a vulnerability in the ngx_http_charset_module module. When charset, source_charset, and charset_map\u00a0and proxy_pass\u00a0with disabled buffering (\u0026quot;off\u0026quot;) directives are configured, unauthenticated attackers can send requests that with conditions beyond the attackers\u0026apos; control to cause a heap buffer over-read in the NGINX worker process, leading to limited disclosure of memory or a restart.\u00a0Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.(CVE-2026-42934)\n\nA vulnerability exists in the ngx_http_scgi_module\u00a0and ngx_http_uwsgi_module\u00a0modules that may result in excessive memory allocation or an over-read of data. When scgi_pass\u00a0or uwsgi_pass\u00a0is configured, an unauthenticated attacker with man-in-the-middle (MITM) ability to control responses from an upstream server may be able to read the memory of the NGINX worker process or restart it.\u00a0 Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.(CVE-2026-42946)",
"id": "OESA-2026-2511",
"modified": "2026-08-06T11:11:27Z",
"published": "2026-05-29T11:11:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2511"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40701"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42934"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42946"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "nginx security update",
"upstream": [
"CVE-2026-40701",
"CVE-2026-42934",
"CVE-2026-42946"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.