# nginx

nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server, and mail proxy server.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## NGINX2Root: F5 patches five critical NGINX vulnerabilities

DevFeed: [NGINX2Root: F5 patches five critical NGINX vulnerabilities](<https://devfeed.tech/articles/nginx2root-f5-patches-five-critical-nginx-vulnerabilities-144172.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/19/nginx2root-nginx-vulnerabilities/>)

Author: Zeljka Zorz

Published: 2026-11-19T18:25:50Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [patches](<https://devfeed.tech/topics/patches.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>)

Tags: [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [f5](<https://devfeed.tech/tags/f5.md>), [f5-networks](<https://devfeed.tech/tags/f5-networks.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [news](<https://devfeed.tech/tags/news.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [palo-alto-networks](<https://devfeed.tech/tags/palo-alto-networks.md>), [patched](<https://devfeed.tech/tags/patched.md>), [patches](<https://devfeed.tech/tags/patches.md>), [poc](<https://devfeed.tech/tags/poc.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [tenable](<https://devfeed.tech/tags/tenable.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-server](<https://devfeed.tech/tags/web-server.md>), [wild](<https://devfeed.tech/tags/wild.md>), [wiz](<https://devfeed.tech/tags/wiz.md>), [xint](<https://devfeed.tech/tags/xint.md>)

### AI overview

F5 patched five NGINX vulnerabilities that may enable remote code execution with the privileges of the worker process if ASLR is disabled or bypassed. They affect HTTP/2, the DNS resolver, HTTP/3/QUIC, and the mail proxy; one requires a specific combination of resolver, request-derived proxy_pass, and mirror directives. No exploitation in the wild was reported, but a public proof of concept exists for CVE-2026-123007. Rapid7's exploit has constraints, including x86-64 glibc, about 128 GB of HTTP/2 traffic, and recovering heap addresses to bypass ASLR; HTTP/2-terminating proxies may impede it. F5 recommends upgrading to fixed NGINX Open Source 1.30.7 or 1.31.9, or NGINX Plus 37.0.8.1 or 37.3.0.1, then restarting NGINX because a configuration reload does not replace the executable. Users of distro packages should check for backported fixes; updates for some other F5 products are available, with others still in progress.

### Source excerpt

F5 has patched five critical vulnerabilities in NGINX, the world's most widely used open-source web server, that can allow remote code execution under certain conditions. Dubbed "NGINX2Root" by Xint researchers, two of the bunch (CVE-2026-123633 and CVE-2026-123007) were also independently unearthed and reported by Rapid7, Wiz, Ikotas Labs, Palo Alto Networks and Metnir researchers. There's no evidence that any of them has been exploited in the wild, and none were on CISA's Known Exploited Vulnerabilities ... More -> The post NGINX2Root: F5 patches five critical NGINX vulnerabilities appeared first on Help Net Security.

## Critical NGINX 'NGINX2Root' bugs let attackers hijack servers

DevFeed: [Critical NGINX 'NGINX2Root' bugs let attackers hijack servers](<https://devfeed.tech/articles/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers-143849.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/>)

Author: Bill Toulas

Published: 2026-11-19T14:57:24Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [container escape](<https://devfeed.tech/topics/container-escape.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>)

Tags: [code-execution](<https://devfeed.tech/tags/code-execution.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-113425](<https://devfeed.tech/tags/cve-2026-113425.md>), [cve-2026-118899](<https://devfeed.tech/tags/cve-2026-118899.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [root](<https://devfeed.tech/tags/root.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-server](<https://devfeed.tech/tags/web-server.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Two critical NGINX HTTP/2 flaws can enable unauthenticated remote code execution on vulnerable servers, and one can be chained with a separate Linux kernel SCTP flaw to escape a Docker container and gain host root access. CVE-2026-123007 causes worker memory corruption and affects versions 1.9.5-1.31.8; CVE-2026-123633 is a use-after-free affecting versions 1.19.7-1.31.8 when HTTP/2 requests are proxied to a backend. Three additional flaws affect HTTP/3 reverse proxying, DNS subrequests, and mail proxy authentication. Fixes are available in NGINX Open Source 1.30.7 and 1.31.9, and NGINX Plus 37.0.8.1 or 37.3.0.1. Disabling HTTP/2 is a temporary mitigation for the two critical flaws only. Exposure depends on configuration, reachability, patch status, and backported fixes; version counts alone do not establish vulnerability. Censys reproduced memory corruption in four flaws but did not achieve remote code execution.

### Source excerpt

Two critical NGINX vulnerabilities dubbed "nginx2root" allow unauthenticated attackers to execute code remotely on vulnerable web servers, with researchers demonstrating how the flaws can be chained with a Linux kernel bug to gain root access. [...]

## CVE-2026-120753 - Eclipse Ditto gateway accepts \`x-ditto-pre-authenticated\` from a URL query parameter, allowing unauthenticated subject impersonation (default Helm chart)

DevFeed: [CVE-2026-120753 - Eclipse Ditto gateway accepts \`x-ditto-pre-authenticated\` from a URL query parameter, allowing unauthenticated subject impersonation (default Helm chart)](<https://devfeed.tech/articles/cve-2026-120753-eclipse-ditto-gateway-accepts-x-ditto-pre-authenticated-from-a-url-query-parameter-allowing-unauthenticated-subject-impersonation-default-helm-chart-143721.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-120753>)

Author: CVEFEED.io; eclipse.org

Published: 2026-11-19T14:48:18Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-120753](<https://devfeed.tech/tags/cve-2026-120753.md>), [ditto](<https://devfeed.tech/tags/ditto.md>), [eclipse](<https://devfeed.tech/tags/eclipse.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [helm](<https://devfeed.tech/tags/helm.md>), [helm-chart](<https://devfeed.tech/tags/helm-chart.md>), [impersonation](<https://devfeed.tech/tags/impersonation.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [policies](<https://devfeed.tech/tags/policies.md>), [policy](<https://devfeed.tech/tags/policy.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [query](<https://devfeed.tech/tags/query.md>), [remote](<https://devfeed.tech/tags/remote.md>), [things](<https://devfeed.tech/tags/things.md>), [url](<https://devfeed.tech/tags/url.md>)

### AI overview

Eclipse Ditto 1.1.0-3.9.8 can allow unauthenticated impersonation when pre-authentication is enabled: the gateway accepts a client-controlled `x-ditto-pre-authenticated` URL query parameter in addition to the trusted proxy header. In the default Helm chart configuration (`global.jwtOnly: false`), nginx skips Basic authentication for requests with a Bearer authorization header; an attacker can pair an invalid token with the query parameter, and pre-authentication occurs before JWT validation. The attacker may then read or modify Things and Policies permitted to the chosen subject. Disable gateway pre-authentication with `ENABLE_PRE_AUTHENTICATION=false`, or set Helm `global.jwtOnly: true`. The excerpt does not provide patch or fixed-version details.

### Source excerpt

CVE ID :CVE-2026-120753 Published : Nov. 19, 2026, 2:48 p.m. | 34 minutes ago Description :In Eclipse Ditto versions 1.1.0 to 3.9.8, when pre-authentication is enabled, the gateway service accepts the pre-authenticated subject not only from the `x-ditto-pre-authenticated` HTTP header set by a trusted reverse proxy, but also from an undocumented `x-ditto-pre-authenticated` URL query parameter that a client can set. A reverse proxy that only overwrites the header therefore does not stop clients from supplying their own subject. With the default configuration of the Ditto Helm chart (`global.jwtOnly: false`, which implicitly enables pre-authentication), the bundled nginx skips HTTP Basic authentication for any request with an `Authorization: Bearer` header and forwards it without the pre-authentication header. An unauthenticated remote attacker can send an invalid Bearer token together with the query parameter to authenticate as any chosen policy subject. Pre-authentication succeeds before the JWT is validated, so the attacker can read and modify Things and Policies with that subject's permissions. As a mitigation, disable pre-authentication in the gateway (`ENABLE_PRE_AUTHENTICATION=false`) or, when using the Helm chart, configure `global.jwtOnly: true`. Severity: 9.1 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Unauthenticated Remote Code Execution in NGINX: HTTP/2 Flaw Lurked for 11 Years

DevFeed: [Unauthenticated Remote Code Execution in NGINX: HTTP/2 Flaw Lurked for 11 Years](<https://devfeed.tech/articles/unauthenticated-remote-code-execution-in-nginx-http-2-flaw-lurked-for-11-years-141944.md>)

Original publisher: [Read original article](<https://joho-todai.com/en/nginx-remote-code-execution-http2-vulnerability/>)

Author: Toru Misaki

Published: 2026-11-19T02:46:10Z

Content type: news

Language: en

Sources: [Joho no Todai](<https://devfeed.tech/sources/joho-no-todai.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>)

Tags: [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-113425](<https://devfeed.tech/tags/cve-2026-113425.md>), [cve-2026-121810](<https://devfeed.tech/tags/cve-2026-121810.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [cve-2026-123634](<https://devfeed.tech/tags/cve-2026-123634.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [memory-safety](<https://devfeed.tech/tags/memory-safety.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Two NGINX HTTP/2 memory-safety flaws can enable unauthenticated remote code execution when HTTP/2 is enabled. CVE-2026-123007, an integer underflow affecting versions 1.9.5-1.31.8, can drive an out-of-bounds copy; CVE-2026-123633 is a use-after-free affecting 1.19.7-1.31.8 when reverse-proxy connection slots are scarce. nginx.org rates them major and medium, while Wiz rates both Critical, so the article advises considering prerequisites and impact alongside ratings. Rapid7 demonstrated exploitation of the first flaw, but its method required about 128 GB of HTTP/2 traffic and specific conditions; that does not rule out other methods. Update open-source NGINX to 1.31.9 or 1.30.7, as applicable, and ensure old workers exit. Check distributor backports and embedded products separately. If an update is delayed, disabling HTTP/2 mitigates these two flaws but does not address the other vulnerabilities in the release.

### Source excerpt

Two memory-safety vulnerabilities have been found in NGINX's HTTP/2 processing that could allow unauthenticated remote code execution. One had existed since version 1.9.5 in 2015, and fixes are available in open-source versions 1.31.9 and 1.30.7.

## NGINX ( HTTP/2 ) - Critical Remote Code Execution Vulnerability (CVE-2026-123007)

DevFeed: [NGINX ( HTTP/2 ) - Critical Remote Code Execution Vulnerability (CVE-2026-123007)](<https://devfeed.tech/articles/nginx-http-2-critical-remote-code-execution-vulnerability-cve-2026-123007-142023.md>)

Original publisher: [Read original article](<https://www.netspi.com/blog/executive-blog/critical-vulnerability/nginx-http-2-critical-remote-code-execution-vulnerability-cve-2026-123007/>)

Author: Team NetSPI

Published: 2026-11-19T00:29:53Z

Content type: news

Language: en

Sources: [NetSPI](<https://devfeed.tech/sources/netspi.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>)

Tags: [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-vulnerability](<https://devfeed.tech/tags/critical-vulnerability.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>)

### AI overview

CVE-2026-123007 is an integer underflow in nginx's HTTP/2 flow-control accounting that can let an unauthenticated remote attacker read or overwrite worker-process memory and potentially execute code. It affects listed nginx Open Source and NGINX Plus releases when HTTP/2 is enabled; HTTP/1.1-only servers and binaries without the HTTP/2 module are not affected. Fixed releases are nginx 1.31.9 or 1.30.7 and NGINX Plus 37.3.0.1 or 37.0.8.1. The notice advises checking bundled and distribution packages against vendor advisories, since version strings may not reflect backported fixes, then restarting nginx or using a supported live binary upgrade; a configuration reload alone is insufficient. If patching is delayed, it gives version-specific steps to disable HTTP/2. No in-the-wild exploitation was reported, though researchers confirmed working unauthenticated RCE against affected builds.

### Source excerpt

F5 has disclosed a critical vulnerability in the HTTP/2 implementation of nginx. A remote, unauthenticated attacker can use this to read and overwrite memory in the nginx worker process and potentially achieve remote code execution, without credentials or user interaction. The post NGINX ( HTTP/2 ) - Critical Remote Code Execution Vulnerability (CVE-2026-123007) appeared first on NetSPI.

## NGINX2Root (CVE-2026-123007): Frequently asked questions about five critical NGINX vulnerabilities

DevFeed: [NGINX2Root (CVE-2026-123007): Frequently asked questions about five critical NGINX vulnerabilities](<https://devfeed.tech/articles/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx-vulnerabilities-141980.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx>)

Author: Alexis Clark

Published: 2026-11-19T00:18:05Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [aslr](<https://devfeed.tech/tags/aslr.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [f5](<https://devfeed.tech/tags/f5.md>), [faq](<https://devfeed.tech/tags/faq.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [github](<https://devfeed.tech/tags/github.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [local-privilege-escalation](<https://devfeed.tech/tags/local-privilege-escalation.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

NGINX2Root refers to five critical NGINX memory-corruption flaws plus a separate, unpatched Linux kernel SCTP use-after-free that Xint says can chain from NGINX worker access to root. CVE-2026-123007 is the most urgent: unauthenticated code execution is possible when HTTP/2 over TLS is enabled. A public PoC exists, but Rapid7 describes it as constrained: it targets x86-64 builds, needs about 128 GB of HTTP/2 traffic, must defeat ASLR, and may fail behind HTTP/2-terminating proxies or on slow connections. F5's November 18, 2026 out-of-band release fixed these five flaws and five others. The source says there were no reports of exploitation in the wild as of that date. Patching is the fix; restart NGINX after upgrading, since a configuration reload does not replace the running executable. Mitigations cover only some flaws: disabling HTTP/2 leaves three of the five NGINX issues unaddressed. For hosts not using SCTP, Xint recommends blocking the kernel SCTP module until a kernel fix is available.

### Source excerpt

Frequently asked questions about five critical NGINX remote code execution vulnerabilities and five additional flaws fixed in F5's November 18 out-of-band release. Key takeaways NGINX2Root is associated with five critical remote code execution vulnerabilities in NGINX, and a separate, unpatched Linux kernel local privilege escalation (LPE) flaw that can be chained with the NGINX bugs to gain root. CVE-2026-123007 is the most urgent of the five. It is an unauthenticated RCE flaw in NGINX's HTTP/2 implementation and requires only HTTP/2 over TLS to be enabled. A PoC is publicly available on GitHub. F5's November 18 release fixed the five NGINX2Root vulnerabilities and five additional NGINX flaws. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding NGINX2Root, a set of five critical remote code execution vulnerabilities in NGINX, and five additional NGINX flaws that F5 fixed in an out-of-band security release on November 18, 2026. FAQ What is NGINX2Root? NGINX2Root is the name Xint (Theori) gave to five critical remote code execution vulnerabilities in NGINX, and a separate, unpatched Linux kernel local privilege escalation (LPE) flaw that Xint says can be chained with the NGINX bugs to gain root. The NGINX flaws are memory-corruption bugs in HTTP/2, HTTP/3, the resolver, and the mail proxy module. Exploitation depends on the specific feature being active, and achieving code execution generally requires ASLR to be absent or defeated. The name is not used by F5 or nginx.org. What are the vulnerabilities associated with NGINX2Root? CVEDescriptionCVSSv4 (F5)CVE-2026-123007NGINX ngx_http_v2_module vulnerability9.2CVE-2026-123633NGINX ngx_http_v2_module vulnerability9.2CVE-2026-123634NGINX resolver vulnerability9.2CVE-2026-121810NGINX ngx_http_v3_module vulnerability9.2CVE-2026-113425NGINX ngx_mail_proxy_module vulnerability9.2 Xint also identified a separate, unpatched Linux kernel SCTP use

## NGINX2Root: Five RCE bugs in NGINX, a Linux kernel path to root, and how to detect exploitation

DevFeed: [NGINX2Root: Five RCE bugs in NGINX, a Linux kernel path to root, and how to detect exploitation](<https://devfeed.tech/articles/nginx2root-five-rce-bugs-in-nginx-a-linux-kernel-path-to-root-and-how-to-detect-exploitation-143965.md>)

Original publisher: [Read original article](<https://webflow.sysdig.com/blog/nginx2root>)

Author: Sysdig Threat Research Team

Published: 2026-11-19T00:00:00Z

Content type: article

Language: en

Sources: [Sysdig](<https://devfeed.tech/sources/sysdig-blog.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Falco](<https://devfeed.tech/topics/falco.md>), [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>)

Tags: [aslr](<https://devfeed.tech/tags/aslr.md>), [aslr-bypass](<https://devfeed.tech/tags/aslr-bypass.md>), [aws](<https://devfeed.tech/tags/aws.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [block](<https://devfeed.tech/tags/block.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container-escape](<https://devfeed.tech/tags/container-escape.md>), [cve-2026-113425](<https://devfeed.tech/tags/cve-2026-113425.md>), [cve-2026-121810](<https://devfeed.tech/tags/cve-2026-121810.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [cve-2026-123634](<https://devfeed.tech/tags/cve-2026-123634.md>), [docker-container-security](<https://devfeed.tech/tags/docker-container-security.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [f5](<https://devfeed.tech/tags/f5.md>), [falco](<https://devfeed.tech/tags/falco.md>), [heap-buffer-overflow](<https://devfeed.tech/tags/heap-buffer-overflow.md>), [ingress-nginx](<https://devfeed.tech/tags/ingress-nginx.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [linux-kernel-sctp-vulnerability](<https://devfeed.tech/tags/linux-kernel-sctp-vulnerability.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-corruption](<https://devfeed.tech/tags/memory-corruption.md>), [memory-safety](<https://devfeed.tech/tags/memory-safety.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx-1-30-7](<https://devfeed.tech/tags/nginx-1-30-7.md>), [nginx-1-31-9](<https://devfeed.tech/tags/nginx-1-31-9.md>), [nginx-http-2-vulnerability](<https://devfeed.tech/tags/nginx-http-2-vulnerability.md>), [nginx-http-3-vulnerability](<https://devfeed.tech/tags/nginx-http-3-vulnerability.md>), [nginx-mail-proxy-vulnerability](<https://devfeed.tech/tags/nginx-mail-proxy-vulnerability.md>), [nginx-plus](<https://devfeed.tech/tags/nginx-plus.md>), [nginx-resolver-use-after-free](<https://devfeed.tech/tags/nginx-resolver-use-after-free.md>), [nginx-security](<https://devfeed.tech/tags/nginx-security.md>), [nginx-vulnerability](<https://devfeed.tech/tags/nginx-vulnerability.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [post-exploitation-detection](<https://devfeed.tech/tags/post-exploitation-detection.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [root](<https://devfeed.tech/tags/root.md>), [root-privilege-escalation](<https://devfeed.tech/tags/root-privilege-escalation.md>), [runtime-detection](<https://devfeed.tech/tags/runtime-detection.md>), [sysdig-secure](<https://devfeed.tech/tags/sysdig-secure.md>), [sysdig-threat-research-team](<https://devfeed.tech/tags/sysdig-threat-research-team.md>)

### AI overview

The excerpt describes five unauthenticated NGINX memory-safety flaws, fixed in NGINX 1.31.9 and 1.30.7, that can enable worker crashes or code execution; a separate unpatched Linux SCTP flaw can escalate worker access to host root, including from a container. No public PoC or in-the-wild exploitation was reported at publication, though researchers reported working exploits. Prioritize patching and restarting NGINX so old workers exit; distribution packages may need backports, and containers must be rebuilt and redeployed. Until patched, disabling HTTP/2 blocks the two HTTP/2 bugs; other workarounds target request-time DNS and mirror/SSI, HTTP/3, or the mail proxy. Blocking the SCTP module can reduce risk where SCTP is unused, but does not unload it if already loaded, cannot help when built into the kernel, and disrupts SCTP workloads. Runtime monitoring can detect post-exploitation processes such as shells or dropped binaries, but Falco sees syscalls rather than malicious HTTP requests.

### Source excerpt

Five NGINX memory-safety bugs and an unpatched Linux kernel SCTP flaw can chain to root. See who's exposed, how to mitigate, and how to detect NGINX2Root.

## NGINX2Root: Patched nginx packages released

DevFeed: [NGINX2Root: Patched nginx packages released](<https://devfeed.tech/articles/nginx2root-patched-nginx-packages-released-144008.md>)

Original publisher: [Read original article](<https://almalinux.org/blog/2026-11-18-nginx2root/>)

Author: Jonathan Wright Infrastructure SIG Lead; ALESCo Member

Published: 2026-11-18T22:35:22Z

Content type: release

Language: en

Sources: [AlmaLinux](<https://devfeed.tech/sources/blog-on-almalinux.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [nginx](<https://devfeed.tech/topics/nginx.md>)

Tags: [almalinux](<https://devfeed.tech/tags/almalinux.md>), [crash](<https://devfeed.tech/tags/crash.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-113425](<https://devfeed.tech/tags/cve-2026-113425.md>), [cve-2026-121810](<https://devfeed.tech/tags/cve-2026-121810.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [cve-2026-123634](<https://devfeed.tech/tags/cve-2026-123634.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [f5](<https://devfeed.tech/tags/f5.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [packages](<https://devfeed.tech/tags/packages.md>), [patched](<https://devfeed.tech/tags/patched.md>), [process](<https://devfeed.tech/tags/process.md>), [run](<https://devfeed.tech/tags/run.md>)

### AI overview

Five nginx memory corruption vulnerabilities can crash worker processes and may allow code execution as the nginx user; F5 rates them Critical on CVSS v4.0. Exposure depends on enabled features: the two HTTP/2 flaws affect the broadest set of installations, while resolver, mail proxy, and HTTP/3 flaws require their respective functions. AlmaLinux backported fixes to supported nginx streams on AlmaLinux 8-10 and Kitten 10, ahead of upstream, and released them directly to production repositories. Retired streams receive no patches; AlmaLinux 8's default nginx:1.14 is among them. Update to the listed package version or later and restart nginx. Until updated, disabling HTTP/2 blocks the two HTTP/2 flaws, but not the other three; this breaks gRPC traffic through nginx. Packages from third-party sources require fixes from their vendors.

### Source excerpt

Five vulnerabilities in nginx, nicknamed NGINX2Root, were disclosed by nginx today: CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-113425, and CVE-2026-121810. Each one can let an unauthenticated attacker crash an nginx worker process, and potentially run code on the server as the nginx user. F5, which maintains nginx, rates all five 9.2 (Critical) on CVSS v4.0 and 8.1 (High) on CVSS v3.1. AlmaLinux 8, 9, and 10 all ship affected nginx versions. The two most widely exposed flaws are in HTTP/2, so any nginx with HTTP/2 turned on is at risk.

## 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers

DevFeed: [10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers](<https://devfeed.tech/articles/10-year-old-nginx-http-2-flaw-lets-unauthenticated-attackers-execute-code-on-servers-141215.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html>)

Author: The Hacker News

Published: 2026-11-18T18:31:17Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [2026](<https://devfeed.tech/tags/2026.md>), [64-bit](<https://devfeed.tech/tags/64-bit.md>), [alpine](<https://devfeed.tech/tags/alpine.md>), [aslr](<https://devfeed.tech/tags/aslr.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-113425](<https://devfeed.tech/tags/cve-2026-113425.md>), [cve-2026-121810](<https://devfeed.tech/tags/cve-2026-121810.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [cve-2026-123634](<https://devfeed.tech/tags/cve-2026-123634.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [log](<https://devfeed.tech/tags/log.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

CVE-2026-123007 affects NGINX's HTTP/2 support and can let an unauthenticated attacker execute code as an NGINX worker when HTTP/2 is enabled. NGINX Open Source releases from 1.9.5 through 1.31.8 are affected; fixes are in 1.31.9 and 1.30.7. The excerpt also lists affected NGINX Plus builds and notes that R34-R36 have no fix listed. Code execution as a worker does not itself grant root; the reported path to root required a separate Linux kernel SCTP flaw. No exploitation in attacks was reported in the excerpt. Temporarily disabling HTTP/2 blocks this flaw and CVE-2026-123633, but not the other three flaws fixed in the same releases. After upgrading, fully restart NGINX or use a live binary upgrade; a reload can leave old workers running. To check exposure, test whether the NGINX origin accepts HTTP/2, including behind a CDN. The excerpt describes exploit constraints: Rapid7's method used about 128 GB of traffic and depended on particular CPU features, while other researchers reported successful tests in different environments. It also lists possible attack indicators, while cautioning that none is proof and clean access logs do not rule out an attack.

### Source excerpt

10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers A flaw in NGINX's HTTP/2 support can allow an attacker to run code on servers with HTTP/2 enabled, without needing to log in. The decade-old flaw, CVE-2026-123007, dubbed "nginx2root," has been presen ... Read more Published Date: Nov 18, 2026 (3 hours, 4 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-123634 CVE-2026-123633 CVE-2026-123007 CVE-2026-121810 CVE-2026-113425 CVE-2026-118383

## NGINX2Root: Five Critical NGINX Flaws Expose Web Servers to Remote Code Execution

DevFeed: [NGINX2Root: Five Critical NGINX Flaws Expose Web Servers to Remote Code Execution](<https://devfeed.tech/articles/nginx2root-five-critical-nginx-flaws-expose-web-servers-to-remote-code-execution-142882.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/nginx2root-five-critical-nginx-flaws-expose-web-servers-to-remote-code-execution/>)

Author: OX Security

Published: 2026-11-18T17:46:02Z

Content type: news

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [distro](<https://devfeed.tech/tags/distro.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [f5](<https://devfeed.tech/tags/f5.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [patch](<https://devfeed.tech/tags/patch.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [research](<https://devfeed.tech/tags/research.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

F5 released fixes on November 18, 2026, for five independent NGINX vulnerabilities that can each allow unauthenticated remote code execution under different configurations. The excerpt identifies exposure paths involving HTTP/2, HTTP/3, proxying, and mail proxy setups. CVE-2026-123007, present since HTTP/2 was introduced in 2015, is described as the most serious; Rapid7 has published a working exploit, though no in-the-wild exploitation is confirmed. Upgrade to 1.31.9 or a distribution package with backported fixes, verify the package against the distro advisory, and restart NGINX after patching. If patching is delayed, disabling HTTP/2 mitigates two of the five flaws, while the others require separate measures: disable HTTP/3, avoid request-phase dynamic upstream resolution, and restrict public mail-proxy access. The excerpt does not detail each vulnerability's configuration requirements.

### Source excerpt

Unauthenticated attackers can run code on NGINX servers through HTTP/2, HTTP/3, proxying and mail proxy setups. Administrators are urged to upgrade to 1.31.9 immediately. On November 18, 2026, F5 released fixes for five NGINX vulnerabilities, which researchers have named nginx2root. Xint's research team found all five, and each one leads to remote code execution on [...] The post NGINX2Root: Five Critical NGINX Flaws Expose Web Servers to Remote Code Execution appeared first on OX Security.

## CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities

DevFeed: [CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities](<https://devfeed.tech/articles/cve-2026-123633-and-cve-2026-123007-critical-nginx-http-2-vulnerabilities-141063.md>)

Original publisher: [Read original article](<https://thecyberthrone.in/2026/11/18/cve-2026-123633-and-cve-2026-123007-critical-nginx-http-2-vulnerabilities/>)

Author: PravinKarthik

Published: 2026-11-18T17:11:35Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [proxy](<https://devfeed.tech/topics/proxy.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [reverse-proxy](<https://devfeed.tech/tags/reverse-proxy.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [web](<https://devfeed.tech/tags/web.md>), [web-server](<https://devfeed.tech/tags/web-server.md>)

### AI overview

Both critical NGINX HTTP/2 vulnerabilities require HTTP/2 to be enabled, but their exposure conditions differ. CVE-2026-123633 is a use-after-free triggered under specific reverse-proxy conditions when worker connections are scarce; CVE-2026-123007 is an HTTP/2 flow-control integer underflow that can cause a heap buffer overflow, including on servers serving static content without a backend or third-party modules. Both may crash workers or corrupt memory, with remote code execution possible under reported conditions. F5 fixes for NGINX Open Source are 1.30.7 (stable) and 1.31.9 (mainline). NGINX Plus requires different releases by CVE: 37.0.7.1 or 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 or 37.3.0.1 for CVE-2026-123007. The text recommends inventorying deployments, checking HTTP/2 and proxy configurations, prioritizing exposed systems, applying updates, and confirming old workers have exited. If patching is delayed, disabling HTTP/2 on affected listeners is a temporary mitigation, not a substitute for updating. Unexpected worker crashes or activity are investigation leads, not confirmed exploitation indicators.

### Source excerpt

CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities NGINX is one of the most widely deployed components in modern web infrastructure. It serves as a web server, reverse proxy and load balancer, handling incoming traffic before forwarding requests to ba ... Read more Published Date: Nov 18, 2026 (2 hours, 14 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-123633 CVE-2026-123007 CVE-2026-114938

## nginx2root: Critical nginx vulnerabilities, including one RCE \[CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425\]

DevFeed: [nginx2root: Critical nginx vulnerabilities, including one RCE \[CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425\]](<https://devfeed.tech/articles/nginx2root-critical-nginx-vulnerabilities-including-one-rce-cve-2026-123007-cve-2026-123634-cve-2026-123633-cve-2026-121810-cve-2026-113425-143873.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/nginx2root-critical-nginx-rce-vulnerabilities>)

Author: Oscar Sanchez Jr.

Published: 2026-11-18T17:11:00Z

Content type: tutorial

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [2018](<https://devfeed.tech/tags/2018.md>), [2026](<https://devfeed.tech/tags/2026.md>), [container](<https://devfeed.tech/tags/container.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-113425](<https://devfeed.tech/tags/cve-2026-113425.md>), [cve-2026-121810](<https://devfeed.tech/tags/cve-2026-121810.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [cve-2026-123634](<https://devfeed.tech/tags/cve-2026-123634.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx-1-31-9](<https://devfeed.tech/tags/nginx-1-31-9.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [rce](<https://devfeed.tech/tags/rce.md>), [threats](<https://devfeed.tech/tags/threats.md>), [update](<https://devfeed.tech/tags/update.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerabilities-threats](<https://devfeed.tech/tags/vulnerabilities-threats.md>)

### AI overview

The excerpt describes five nginx vulnerabilities and a Linux SCTP kernel flaw that can be chained for root access, including from a Docker container. CVE-2026-123007 affects nginx 1.9.5-1.31.8 when reachable HTTP/2 is enabled. Other flaws target resolver subrequests, HTTP/2 or HTTP/3 connections, and mail proxy authentication. Update to nginx 1.31.9 or 1.30.7; distro packages may backport fixes without changing the reported version, so check security advisories. Disabling HTTP/2 mitigates only CVE-2026-123007 and CVE-2026-123633; other temporary mitigations depend on the flaw, including removing request-time DNS, disabling QUIC, or restricting mail proxy listeners. Archived ingress-nginx bundles its own vulnerable nginx and has no upstream fix. Disabling SCTP via modprobe applies only if SCTP is not already loaded or built into the kernel.

### Source excerpt

nginx2root is five critical nginx RCE vulnerabilities, including CVE-2026-123007 in HTTP/2. Check if you're affected and update to nginx 1.31.9 or 1.30.7. Category: Vulnerabilities & Threats

## CVE-2026-123007 - NGINX ngx\_http\_v2\_module vulnerability

DevFeed: [CVE-2026-123007 - NGINX ngx\_http\_v2\_module vulnerability](<https://devfeed.tech/articles/cve-2026-123007-nginx-ngx-http-v2-module-vulnerability-140818.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-123007>)

Author: cvefeed.io

Published: 2026-11-18T16:18:04Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [heap overflow](<https://devfeed.tech/topics/heap-overflow.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [aslr](<https://devfeed.tech/tags/aslr.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [code](<https://devfeed.tech/tags/code.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [crash](<https://devfeed.tech/tags/crash.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [data](<https://devfeed.tech/tags/data.md>), [f5](<https://devfeed.tech/tags/f5.md>), [flow](<https://devfeed.tech/tags/flow.md>), [flow-control](<https://devfeed.tech/tags/flow-control.md>), [heap](<https://devfeed.tech/tags/heap.md>), [http](<https://devfeed.tech/tags/http.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [impact](<https://devfeed.tech/tags/impact.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx-open-source](<https://devfeed.tech/tags/nginx-open-source.md>), [nginx-plus](<https://devfeed.tech/tags/nginx-plus.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CVE-2026-123007 affects NGINX Plus and NGINX Open Source configurations using HTTP/2. Processing undisclosed traffic can push the flow control window past its allowed threshold, potentially causing a heap buffer overflow and worker segmentation fault. The stated impacts include crashing a worker, corrupting memory, and potentially remote code execution when ASLR is disabled or bypassed. The excerpt describes this as a data-plane issue with no control-plane exposure. It does not identify affected versions or provide remediation details.

### Source excerpt

CVE ID :CVE-2026-123007 Published : Nov. 18, 2026, 4:18 p.m. | 15 minutes ago Description :This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## NGINX2Root: Remote Code Execution vulnerabilities in nginx

DevFeed: [NGINX2Root: Remote Code Execution vulnerabilities in nginx](<https://devfeed.tech/articles/nginx2root-remote-code-execution-vulnerabilities-in-nginx-140989.md>)

Original publisher: [Read original article](<https://lwn.net/Articles/1108362/>)

Author: jzb

Published: 2026-11-18T16:13:34Z

Content type: news

Language: en

Sources: [LWN.net](<https://devfeed.tech/sources/lwn-net.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [container escape](<https://devfeed.tech/topics/container-escape.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [code-execution](<https://devfeed.tech/tags/code-execution.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-container](<https://devfeed.tech/tags/docker-container.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [kernel-vulnerability](<https://devfeed.tech/tags/kernel-vulnerability.md>), [linux](<https://devfeed.tech/tags/linux.md>), [lpe](<https://devfeed.tech/tags/lpe.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [shell](<https://devfeed.tech/tags/shell.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Xint reports five critical NGINX vulnerabilities; the most severe reportedly lets an unauthenticated attacker execute commands on a server with HTTP/2 enabled. Chaining this with an SCTP kernel privilege-escalation flaw introduced in Linux 4.15 could give the attacker root access. Xint says it obtained a root shell in a Docker setup, and warns that reachable SCTP can expose the shared host kernel and other containers. SCTP availability depends on the kernel, installed modules, and container restrictions; a kernel patch was not yet available. Xint recommends updating to NGINX 1.31.9 and blocking the SCTP module on hosts that do not need it until a kernel fix is released.

### Source excerpt

Xint is reporting that it has discovered a collection of five critical vulnerabilities in the NGINX web server. The worst flaw, it says, would allow an unauthenticated attacker to execute commands on an affected nginx server with HTTP/2 enabled. The company also reports a local-privilege escalation (LPE) kernel vulnerability, which was introduced in the 4.15 kernel, in the Stream Control Transmission Protocol (SCTP) subsystem. If chained with the NGINX vulnerability, it would allow an attacker to gain root privileges on the host. A kernel patch for this is not yet available. We also obtained a root shell on the host in a setup where nginx was running in a Docker container. On many Linux distributions, the SCTP module is installed by default and the kernel loads it automatically the first time a program opens an SCTP socket. Whether SCTP is reachable on a given host still depends on the kernel, the available modules, and the container's restrictions. Where it is reachable, the attacker can take over the host kernel. Since all containers on the host share that kernel, this gives the attacker control of the host and every container on it. Xint recommends updating to NGINX 1.31.9, which was just released, and to block the SCTP module on hosts that do not need it until a kernel fix is available. See the mitigations section of their report for more information.

## Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007

DevFeed: [Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007](<https://devfeed.tech/articles/unauthenticated-remote-code-execution-in-nginx-cve-2026-123633-and-cve-2026-123007-141238.md>)

Original publisher: [Read original article](<https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities>)

Author: Tomer Schwartz

Published: 2026-11-18T15:13:20Z

Content type: news

Language: en

Sources: [Wiz](<https://devfeed.tech/sources/wiz-blog-rss-feed.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cve-2026-123633](<https://devfeed.tech/tags/cve-2026-123633.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [research](<https://devfeed.tech/tags/research.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Two critical NGINX HTTP/2 flaws, CVE-2026-123633 and CVE-2026-123007, can enable unauthenticated remote code execution on affected servers. One is a use-after-free when a request is processed on a connection still marked reusable; the other stems from flow-control accounting that can underflow and lead to an out-of-bounds memory copy. Both require HTTP/2, but CVE-2026-123633 involves reverse-proxy processing when connection slots run low, while CVE-2026-123007 was demonstrated on 64-bit HTTPS servers serving static files without backend apps or third-party modules. A compromised NGINX instance can expose multiple sites or APIs behind it. Identify affected deployments and upgrade to a fixed release; if upgrading is delayed, temporarily disable HTTP/2, test compatibility, reload NGINX, and confirm old workers have exited. Investigate unexpected worker crashes or commands launched by NGINX as general warning signs, not confirmed indicators. The researchers report proof-of-concept exploitation in lab settings but say they are not releasing the exploits.

### Source excerpt

Two critical HTTP/2 flaws can allow attackers to compromise NGINX servers, putting the websites, APIs, and sensitive data they handle at risk.

## CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)

DevFeed: [CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)](<https://devfeed.tech/articles/cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed-141104.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed>)

Author: Stephen Fewer

Published: 2026-11-18T13:56:42Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [docker](<https://devfeed.tech/tags/docker.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [f5](<https://devfeed.tech/tags/f5.md>), [flow-control](<https://devfeed.tech/tags/flow-control.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [linux](<https://devfeed.tech/tags/linux.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [memory](<https://devfeed.tech/tags/memory.md>), [network](<https://devfeed.tech/tags/network.md>), [network-bandwidth](<https://devfeed.tech/tags/network-bandwidth.md>), [network-traffic](<https://devfeed.tech/tags/network-traffic.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [research](<https://devfeed.tech/tags/research.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-disclosure](<https://devfeed.tech/tags/vulnerability-disclosure.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

CVE-2026-123007 is a critical nginx HTTP/2 integer underflow that can enable unauthenticated code execution in the nginx worker under specific conditions. Rapid7's proof of concept worked on a Linux/amd64 nginx 1.31.8 Docker image with HTTP/2 and TLS enabled. The exploit cancels queued response data, causing nginx to restore flow-control credit above the HTTP/2 limit; a later unsigned subtraction underflows, and excessive credit becomes an invalid response length that can trigger out-of-bounds memory access during buffered TLS copying. Exploitation requires about 128 GB of HTTP/2 traffic in the overview; the analysis estimates about 119 GiB plaintext for the demonstrated route, plus TLS and network overhead. Bandwidth and nginx's default one-hour connection lifetime constrain feasibility, and proxied HTTP/2 frames may not preserve the required pattern. The demonstrated copy behavior also depends on a specific x86-64 glibc EVEX/YMM implementation and CPU features; other viable RCE methods are not known. Impact is limited to the worker's permissions. The excerpt says vendor fixes are available but does not identify versions or patch steps.

### Source excerpt

Overview Today, both Rapid7 and F5 are disclosing CVE-2026-123007, a critical integer underflow vulnerability affecting nginx HTTP/2, which can allow for unauthenticated remote code execution (RCE) against affected servers under certain conditions. CVE ID Description CWE CVSSv4 CVE-2026-123007 HTTP/2 flow-control memory corruption permitting worker-context RCE CWE-191 (Integer Underflow) 9.2 (Critical) nginx can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can exploit this error by cancelling queued response data, then make nginx use an invalid length when copying a later response. The resulting memory corruption can disclose data, interrupt service, and execute code with the nginx worker process's permissions. Impact Rapid7 has developed a proof-of-concept to demonstrate leveraging CVE-2026-123007 for unauthenticated RCE against a vulnerable linux/amd64 Docker image running nginx version 1.31.8, as shown below in Figure 1. The target nginx server's configuration had http2 on and TLS enabled. Note that for brevity, video playback is at 8x speed. Figure 1: Video demonstrating unauthenticated RCE against NGINX 1.31.8 via CVE-2026-123007 Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data. Both available network bandwidth and connection timeouts will place practical limitations on Internet exploitation. In the above example shown in Figure 1, exploitation takes two and a half minutes. The approximate timings to transmit the required network data over a 10 Gbit/s network is two minutes, while on a 1 Gbit/s network it is seventeen minutes. Due to nginx's default one hour connection lifetime, a network slower than approximately 300 Mbit/s will take over the one hour connection limit threshold and will not be able to succeed. Additionally, should an HTTP/2 connection be proxied, the precise attacker-controlled HTTP/2 frames

## Hackers backdoor Linux servers using trojanized CWP web server

DevFeed: [Hackers backdoor Linux servers using trojanized CWP web server](<https://devfeed.tech/articles/hackers-backdoor-linux-servers-using-trojanized-cwp-web-server-119362.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/hackers-backdoor-linux-servers-using-trojanized-cwp-web-server/>)

Author: Bill Toulas

Published: 2026-11-05T16:24:26Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [Remote Access Trojan](<https://devfeed.tech/topics/remote-access-trojan.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>)

Tags: [backdoor](<https://devfeed.tech/tags/backdoor.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [control-web-panel](<https://devfeed.tech/tags/control-web-panel.md>), [cwp](<https://devfeed.tech/tags/cwp.md>), [cwpdoor](<https://devfeed.tech/tags/cwpdoor.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [web-server](<https://devfeed.tech/tags/web-server.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

CWPdoor is installed by a script posing as an updater that replaces cwpsrv versions 1.15.10 or 1.24.0 with a malicious binary, then hides the change by restoring timestamps, deleting temporary files and wiping command history. It remains dormant until a specially crafted HTTP request supplies an encrypted command, timestamp and RSA signature. The backdoor checks that the timestamp is within five minutes and verifies the signature before decrypting and executing the command; it also suppresses the triggering request from access logs. XLab recommends checking for the ngx_http_integrity_helper Unix socket, suspicious cwpsrv helper processes and X-Ngx-Integrity strings in the binary. If compromise is confirmed, replace the binary with a legitimate copy, upgrade CWP, rotate control panel credentials and investigate for additional malware. The excerpt says the connection between CWPdoor and Ebury remains unclear.

### Source excerpt

A new Linux malware called CWPdoor is being distributed through a trojanized version of cwpsrv, the web server behind the Control Web Panel (CWP) management interface. [...]

## Call for testing - nginx fix for "no buffer space in script copy" errors

DevFeed: [Call for testing - nginx fix for "no buffer space in script copy" errors](<https://devfeed.tech/articles/call-for-testing-nginx-fix-for-no-buffer-space-in-script-copy-errors-118942.md>)

Original publisher: [Read original article](<https://almalinux.org/blog/2026-11-04-nginx-script-copy-fix-call-for-testing/>)

Author: Andrew Lukoshko AlmaLinux Lead Architect

Published: 2026-11-04T00:00:00Z

Content type: release

Language: en

Sources: [AlmaLinux](<https://devfeed.tech/sources/blog-on-almalinux.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [staging](<https://devfeed.tech/topics/staging.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>)

Tags: [cve](<https://devfeed.tech/tags/cve.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [packages](<https://devfeed.tech/tags/packages.md>), [regression](<https://devfeed.tech/tags/regression.md>), [repository](<https://devfeed.tech/tags/repository.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The CVE-2026-42533 nginx update caused intermittent HTTP 500 errors on configurations where a `set` or `rewrite` uses a `volatile` map whose value contains variables. The backport stored the script buffer boundary in a global variable; a nested map script could overwrite it, so the outer script checked against the wrong buffer. AlmaLinux's testing packages save and restore that boundary around script execution, preserving the CVE protection and ABI while fixing nested scripts. To test, install `almalinux-release-testing`, upgrade nginx and installed nginx modules from `almalinux-testing`, verify the package version for your release, then run `nginx -t` and restart nginx. Check the error log after normal traffic for new alerts. The update does not restart nginx automatically; the article advises against leaving the testing repository enabled on production systems and requests reports of both failures and successful testing.

### Source excerpt

The recent nginx security update for CVE-2026-42533 introduced a regression: on some configurations, nginx randomly answers a small share of requests with HTTP 500 and logs [alert] ... no buffer space in script copy. Users reported it to us after updating, and we were able to reproduce it on every AlmaLinux release that received the update. We've found the root cause and built fixed nginx packages that remove the regression while keeping the CVE-2026-42533 fix fully in place. The packages are now in the AlmaLinux testing repository, and we need your help testing them before they go to production.

## One Word Fixed a 60-Second nginx Delay

DevFeed: [One Word Fixed a 60-Second nginx Delay](<https://devfeed.tech/articles/one-word-fixed-a-60-second-nginx-delay-112287.md>)

Original publisher: [Read original article](<https://blog.devops.dev/one-word-fixed-a-60-second-nginx-delay-a25e16b7f210?source=rss----33f8b2d9a328---4>)

Author: DRAVID KUMAR

Published: 2026-11-01T20:01:02Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [cURL](<https://devfeed.tech/topics/curl.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [all](<https://devfeed.tech/tags/all.md>), [assets](<https://devfeed.tech/tags/assets.md>), [auth](<https://devfeed.tech/tags/auth.md>), [bash](<https://devfeed.tech/tags/bash.md>), [browser](<https://devfeed.tech/tags/browser.md>), [but](<https://devfeed.tech/tags/but.md>), [command](<https://devfeed.tech/tags/command.md>), [connect](<https://devfeed.tech/tags/connect.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [curl](<https://devfeed.tech/tags/curl.md>), [days](<https://devfeed.tech/tags/days.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [delay](<https://devfeed.tech/tags/delay.md>), [devops](<https://devfeed.tech/tags/devops.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [linux](<https://devfeed.tech/tags/linux.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [one](<https://devfeed.tech/tags/one.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [word](<https://devfeed.tech/tags/word.md>)

### AI overview

An nginx reverse proxy caused intermittent 60-second delays on Google sign-in because `localhost` resolved to both IPv6 and IPv4. On slow requests nginx tried `[::1]:5000`, where no service was listening, waited for its 60-second connection timeout, then retried the working IPv4 address. Direct requests to the app were fast, and the nginx error log recorded upstream connection timeouts. Replacing `proxy_pass http://localhost:5000;` with `proxy_pass http://127.0.0.1:5000;` resolved the stalls in the reported checks: five slow requests in a 15-request sample before, none in nine requests after, plus a successful browser sign-in. The author could not confirm what triggered the issue two days earlier. As prevention, the account recommends using explicit IPv4 addresses for local nginx upstreams, monitoring timeout logs, and considering a shorter `proxy_connect_timeout`; these steps are reported recommendations, not further tested outcomes.

### Source excerpt

Part of my ongoing DevOps series. Previously: Flask on VPS | Grafana Reverse Proxy | Linux LVM NOTE: This is a real production incident. Domain names and service names are changed. Every command below was actually run -- nothing is theoretical. The Symptom: Users Were Waiting a Full Minute to Sign In Every third Google sign-in request to auth.example.com stalled for about 60 seconds. Users clicked "Sign in with Google" and the page just sat there. Some waited. Some retried. Some probably gave up and never came back. Google sign-in had worked normally until about two days earlier. Here's what made it maddening: Nothing visibly failed. No error pages, no crashes. Every sign-in eventually succeeded -- only a minute late. Google wasn't slow. Google's own pages loaded in about 1 second. Most callbacks were fast. All static assets on the main site were under 0.3 seconds. It was intermittent. Exactly every third request. A pattern, not randomness. And the one detail that kept me up at night: email/password login worked perfectly. It went straight to the auth service inside Docker and never touched this nginx route. So the problem was isolated. But hidden. The Investigation: Seven Steps to the Truth Each step ruled something out. Here's exactly how we narrowed it down. Step 1: Browser HAR -- The First Clue Captured during a slow sign-in: MeasurementResultGET /auth/google60,165 msDNS + connect + TLS~40 msGoogle's pages~1.0 sCallback~0.5 s Ruled out: The network and Google. The delay is on our auth server. Step 2: Single Curl -- The Problem Is Intermittentcurl -w "Time: %{time_total}s\n" -o /dev/null -s "https://auth.example.com/auth/google" Result: 302 in 0.34 s. Showed: The problem is intermittent, not constant. One request proves nothing. Step 3: Curl Loop -- The Pattern Emerges bash for i in {1..15}; do curl -w "Request $i: %{time_total}s\n" -o /dev/null -s "https://auth.example.com/auth/google" sleep 20 done Result: RequestTime160.2 s20.8 s31.2 s460.7 s50.4 s60.9 s760.1 s80.3

## CVE-2026-96631 - AdminNeo Cookie Attribute Injection Vulnerability

DevFeed: [CVE-2026-96631 - AdminNeo Cookie Attribute Injection Vulnerability](<https://devfeed.tech/articles/cve-2026-96631-adminneo-cookie-attribute-injection-vulnerability-109666.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-96631>)

Author: cvefeed.io

Published: 2026-10-30T22:52:47Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Cookies](<https://devfeed.tech/topics/cookies.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [proxy](<https://devfeed.tech/topics/proxy.md>), [nginx](<https://devfeed.tech/topics/nginx.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [admin](<https://devfeed.tech/tags/admin.md>), [allows](<https://devfeed.tech/tags/allows.md>), [cookie](<https://devfeed.tech/tags/cookie.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-96631](<https://devfeed.tech/tags/cve-2026-96631.md>), [database](<https://devfeed.tech/tags/database.md>), [domain](<https://devfeed.tech/tags/domain.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [header](<https://devfeed.tech/tags/header.md>), [http](<https://devfeed.tech/tags/http.md>), [influence](<https://devfeed.tech/tags/influence.md>), [man-in-the-middle](<https://devfeed.tech/tags/man-in-the-middle.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [reverse-proxy](<https://devfeed.tech/tags/reverse-proxy.md>), [scope](<https://devfeed.tech/tags/scope.md>), [session](<https://devfeed.tech/tags/session.md>), [set](<https://devfeed.tech/tags/set.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The excerpt reports that AdminNeo versions 4.6.0 through at least 5.5.0 may allow cookie attribute injection when an attacker can control the `X-Forwarded-Prefix` header. AdminNeo prepends the header to `REQUEST_URI`, then uses that value in cookie paths without escaping semicolons; PHP's session cookie path is also derived from it. Injected attributes can broaden cookie scope, potentially exposing the `neo_sid` session ID and `neo_key` database-password encryption key, and can alter cookie behavior. Suggested mitigations are to sanitize the prefix and URI, use PHP `setcookie()` or `setrawcookie()` instead of constructing `Set-Cookie` manually, and configure the reverse proxy to set a static trusted prefix rather than forward client input. This summary reflects the supplied excerpt.

### Source excerpt

CVE ID :CVE-2026-96631 Published : Oct. 30, 2026, 10:52 p.m. | 9 hours, 45 minutes ago Description :### Summary AdminNeo versions 4.6.0 through at least 5.5.0 are vulnerable to cookie attribute injection via the `X-Forwarded-Prefix` HTTP header. An attacker who can influence this header (e.g., through a reverse proxy that forwards it from clients, an attacker-controlled upstream proxy, or a man-in-the-middle position) can inject arbitrary cookie attributes including `Domain`, `Path`, `Secure`, and `SameSite` into all `Set-Cookie` response headers emitted by AdminNeo. This allows an attacker to expand the cookie scope to an attacker-controlled domain (e.g., `Domain=.evil.com`), causing the victim's browser to send AdminNeo's `neo_sid` (session ID) and `neo_key` (database password encryption key) cookies to the attacker's server on subsequent requests. Originally reported by @retkoussa in Adminer: https://github.com/vrana/adminer/security/advisories/GHSA-c533-9qwm-8w5h ### Vulnerable Code **Root cause 1 - Unsanitized header prepended to `REQUEST_URI`** (`admin/include/bootstrap.inc.php`, lines 50-52): ```php if ($_SERVER["HTTP_X_FORWARDED_PREFIX"]) { $_SERVER["REQUEST_URI"] = $_SERVER["HTTP_X_FORWARDED_PREFIX"] . $_SERVER["REQUEST_URI"]; } ``` The client-supplied `X-Forwarded-Prefix` header is concatenated into `REQUEST_URI` with no validation or sanitization of special characters (specifically semicolons, which delimit cookie attributes). **Root cause 2 - Manual `Set-Cookie `header construction without escaping** (`admin/include/functions.inc.php`, lines 416-424): ```php function cookie(string $name, string $value, int $lifetime = 2592000): void { header("Set-Cookie: $name=" . rawurlencode($value) . ($lifetime ? "; expires=" . gmdate("D, d M Y H:i:s", time() + $lifetime) . " GMT" : "") . "; path=" . preg_replace('~\?.*~', '', $_SERVER["REQUEST_URI"]) . (HTTPS ? "; secure" : "") . "; HttpOnly; SameSite=lax", false); } ``` The tainted `REQUEST_URI` is interpolated dire

## System Design in 6 Points, Explained with a Chai Stall That Went Viral

DevFeed: [System Design in 6 Points, Explained with a Chai Stall That Went Viral](<https://devfeed.tech/articles/system-design-in-6-points-explained-with-a-chai-stall-that-went-viral-104372.md>)

Original publisher: [Read original article](<https://ihatereading.in/blogs/system-design-in-6-points-explained-with-a-chai-stall>)

Author: Shrey Vijayvargiya

Published: 2026-10-28T09:00:00Z

Content type: tutorial

Language: en

Sources: [iHateReading](<https://devfeed.tech/sources/ihatereading.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [least connections](<https://devfeed.tech/topics/least-connections.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [api](<https://devfeed.tech/tags/api.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [backblaze-b2](<https://devfeed.tech/tags/backblaze-b2.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backups](<https://devfeed.tech/tags/backups.md>), [batching](<https://devfeed.tech/tags/batching.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [bsd](<https://devfeed.tech/tags/bsd.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cache-control](<https://devfeed.tech/tags/cache-control.md>), [cache-vs-queue](<https://devfeed.tech/tags/cache-vs-queue.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [coding](<https://devfeed.tech/tags/coding.md>), [development](<https://devfeed.tech/tags/development.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [load-balancer-explained](<https://devfeed.tech/tags/load-balancer-explained.md>), [logs](<https://devfeed.tech/tags/logs.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [product](<https://devfeed.tech/tags/product.md>), [programming](<https://devfeed.tech/tags/programming.md>), [queue](<https://devfeed.tech/tags/queue.md>), [react](<https://devfeed.tech/tags/react.md>), [read-replicas](<https://devfeed.tech/tags/read-replicas.md>), [read-replicas-explained](<https://devfeed.tech/tags/read-replicas-explained.md>), [retries](<https://devfeed.tech/tags/retries.md>), [retries-with-exponential-backoff-and-jitter](<https://devfeed.tech/tags/retries-with-exponential-backoff-and-jitter.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [system-design-basics](<https://devfeed.tech/tags/system-design-basics.md>), [system-design-cheat-sheet](<https://devfeed.tech/tags/system-design-cheat-sheet.md>), [system-design-for-beginners](<https://devfeed.tech/tags/system-design-for-beginners.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

The article explains six system design patterns through a viral chai stall: cache repeated reads, queue slow background work, balance traffic across healthy app servers, use read replicas for read scaling, store files in object storage behind a CDN, and add timeouts, bounded jittered retries, and structured logs around network calls. It describes key limits: caches can serve stale data and need shared storage across servers; queues defer work and require durable jobs, idempotency, and monitoring; load balancers need shared sessions and can expose database connection limits; asynchronous replicas lag and do not reduce write load; file storage has provider-specific egress costs and private files need signed URLs; retries can duplicate unsafe operations or multiply across layers. Suggested order: logs and timeouts, object storage/CDN, then cache, queue, load balancer, and replicas after query and index fixes.

### Source excerpt

System design basics in six points: cache, queue, load balancer, read replicas, object storage + CDN, and retries with timeouts and logs. One chai stall story,...

## CORS Error Fix: Diagnose Console Errors and Configure Headers

DevFeed: [CORS Error Fix: Diagnose Console Errors and Configure Headers](<https://devfeed.tech/articles/cors-error-fix-diagnose-console-errors-and-configure-headers-93002.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/cors-error-fix-troubleshooting-playbook/>)

Author: SitePoint Team

Published: 2026-10-21T15:42:54Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [nginx](<https://devfeed.tech/topics/nginx.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [added](<https://devfeed.tech/tags/added.md>), [apply](<https://devfeed.tech/tags/apply.md>), [browser](<https://devfeed.tech/tags/browser.md>), [configure](<https://devfeed.tech/tags/configure.md>), [console](<https://devfeed.tech/tags/console.md>), [cors](<https://devfeed.tech/tags/cors.md>), [development](<https://devfeed.tech/tags/development.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [error](<https://devfeed.tech/tags/error.md>), [errors](<https://devfeed.tech/tags/errors.md>), [express](<https://devfeed.tech/tags/express.md>), [headers](<https://devfeed.tech/tags/headers.md>), [messages](<https://devfeed.tech/tags/messages.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [programming](<https://devfeed.tech/tags/programming.md>), [reading](<https://devfeed.tech/tags/reading.md>), [responses](<https://devfeed.tech/tags/responses.md>), [server](<https://devfeed.tech/tags/server.md>), [using](<https://devfeed.tech/tags/using.md>), [web](<https://devfeed.tech/tags/web.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

CORS errors can arise because the server omits required headers, mishandles an OPTIONS preflight, redirects the preflight, or combines wildcard origins with credentialed requests. The excerpt recommends reading the browser console message, reproducing preflight with curl, and matching the response to the cause. During development, a Vite proxy makes API calls appear same-origin, but it does not replace production CORS configuration. For production, it gives examples for Express, Next.js and Nginx that use explicit origin allowlists, handle OPTIONS, and return appropriate headers; Express middleware handles preflights at app level, while Next.js examples define an OPTIONS handler or middleware. It cautions against reflecting unvalidated origins, using `*` with credentials, Nginx header inheritance pitfalls, and setting CORS headers in both the application and proxy. Verify headers on both preflight and actual responses.

### Source excerpt

Diagnose browser CORS errors from console messages and preflight responses, then apply secure fixes using development proxies or server-side headers in Express, Next.js, and Nginx. Continue reading CORS Error Fix: Diagnose Console Errors and Configure Headers on SitePoint.

## F5 releases out-of-band patches for critical NGINX vulnerabilities

DevFeed: [F5 releases out-of-band patches for critical NGINX vulnerabilities](<https://devfeed.tech/articles/f5-releases-out-of-band-patches-for-critical-nginx-vulnerabilities-90019.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/f5-releases-out-of-band-patches-for-critical-nginx-vulnerabilities/>)

Author: Sergiu Gatlan

Published: 2026-10-19T13:49:24Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [patches](<https://devfeed.tech/topics/patches.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Security research](<https://devfeed.tech/topics/security-research.md>)

Tags: [code-execution](<https://devfeed.tech/tags/code-execution.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [critical](<https://devfeed.tech/tags/critical.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [dos](<https://devfeed.tech/tags/dos.md>), [f5](<https://devfeed.tech/tags/f5.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [out-of-band](<https://devfeed.tech/tags/out-of-band.md>), [patches](<https://devfeed.tech/tags/patches.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

F5 released out-of-band patches for multiple NGINX products addressing several vulnerabilities, including three critical flaws that may allow remote attackers to cause denial of service or execute code under specified conditions. The article describes affected configurations, mitigations for administrators who cannot patch immediately, and the absence of a claim that these issues have been exploited in the wild.

### Source excerpt

F5 has released out-of-band security patches to address multiple NGINX web server flaws, including three critical-severity vulnerabilities that can let attackers execute code on vulnerable systems. [...]

## HTTP1 vs HTTP2 vs HTTP3

DevFeed: [HTTP1 vs HTTP2 vs HTTP3](<https://devfeed.tech/articles/http1-vs-http2-vs-http3-88189.md>)

Original publisher: [Read original article](<https://newsletter.systemdesign.one/p/http-concepts-explained>)

Author: Neo Kim

Published: 2026-10-15T12:07:10Z

Content type: article

Language: en

Sources: [System Design Newsletter](<https://devfeed.tech/sources/system-design-newsletter.md>)

Topics: [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [cURL](<https://devfeed.tech/topics/curl.md>)

Tags: [congestion-control](<https://devfeed.tech/tags/congestion-control.md>), [http2](<https://devfeed.tech/tags/http2.md>)

### AI overview

The article explains HTTP performance through connection setup, persistent connections, pipelining, head-of-line blocking, streaming, caching, TCP slow start, and HTTP/2 framing. It connects these mechanisms to practical debugging and configuration using browser tools, curl, and web servers. Further discussion of HTTP/2 and HTTP/3 is deferred to Part 2.

### Source excerpt

#190: Part 1 - 23 Concepts Every Engineer Should Know

[Next page](<https://devfeed.tech/topics/nginx.md?cursor=WyIyMDI2LTEwLTE1VDEyOjA3OjEwKzAwOjAwIiwgIjM2NjljM2E2LWU4YjYtNDViZC1hMWY2LWJkYWM5OTY3ZTJjMiJd>)