#1136·openresty

CVE-2026-42530 & CVE-2026-42055 & CVE-2026-48142

Author: abolinhasCreated Jun 18, 2026Updated Aug 26, 2026

Openresty right now is vulnerable to:

 *) Security: use-after-free might occur when using HTTP/3 and processing
       a specially crafted QUIC session, allowing an attacker to cause
       worker process memory corruption or segmentation fault in a worker
       process (**CVE-2026-42530**).
       Thanks to Trung Nguyen of CyStack.

    *) Security: a heap memory buffer overflow might occur in a worker
       process when using a configuration with "ignore_invalid_headers off;"
       and "large_client_header_buffers" with large configured values when
       proxying a specially crafted request to HTTP/2 or gRPC backend,
       allowing an attacker to cause worker process memory corruption or
       segmentation fault in a worker process (**CVE-2026-42055**).
       Thanks to Mufeed VH of Winfunc Research.

    *) Security: a heap memory buffer overread might occur in a worker
       process while handling a specially sent response with decoding from
       UTF-8 via the "charset_map" directive, allowing an attacker to cause
       a limited disclosure of worker proccess memory or segmentation fault
       in a worker process (**CVE-2026-48142**).
       Thanks to Han Yan of Xiaomi and p4p3r of CYBERONE

Bumping openresty to nginx 1.31.2+ should mitigate this . Is there any scheduled date to release a new openresty version with nginx 1.31.2 or alternatively any backport?