Response Status for Multiple Vulnerabilities in nginx HTTP/2 Processing (CVE-2026-123633, CVE-2026-123007)
Published: 2026-11-19
This notice describes Kuroco's response status for multiple vulnerabilities in nginx HTTP/2 processing (CVE-2026-123633, CVE-2026-123007).
These vulnerabilities may allow an unauthenticated attacker to execute arbitrary code on nginx servers with HTTP/2 enabled. Both are rated Critical (CVSS 4.0: 9.2).
This notice also covers three other nginx vulnerabilities disclosed at the same time (CVE-2026-123634, CVE-2026-121810, CVE-2026-113425).
Response status
These vulnerabilities require HTTP/2 to be enabled in nginx. The nginx used by Kuroco is not configured to use HTTP/2, so we have determined that Kuroco is not affected.
CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425 are not blocked by disabling HTTP/2. Each of them affects only the following configuration.
| CVE | Affected configuration |
|---|---|
| CVE-2026-123634 | resolver is used with a proxy_pass whose destination is determined per request, together with a feature that creates subrequests, such as mirror |
| CVE-2026-121810 | HTTP/3 is enabled and requests are forwarded to an upstream (backend) server |
| CVE-2026-113425 | The mail proxy is used with proxy on and auth_http |
The nginx used by Kuroco does not have any of these configurations, so we have determined that Kuroco is not affected.
We will promptly apply the fixed version of nginx as soon as it becomes available.
References
- NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching (Xint)
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 (Wiz)
- nginx Security Advisories
Contact
If you have any questions regarding this matter, please contact Kuroco support.
Related Documents
Support
If you have any other questions, please contact us or check out Our Slack Community.