SecPod

Learn Search

Search across all Learn content

← Back to Security Research
10 NGINX Vulnerabilities Disclosed in November 2026: Impact, Exploit Status, and Remediation

10 NGINX Vulnerabilities Disclosed in November 2026: Impact, Exploit Status, and Remediation

Nov 19, 2026By Shwetha B S

Research cutoff: November 19, 2026

Overview

On November 18, 2026, F5 disclosed ten vulnerabilities affecting NGINX Open Source and NGINX Plus, with certain issues also affecting products incorporating NGINX. The vulnerabilities include memory corruption, denial of service, client-certificate verification bypass, and routing restriction bypass. Exposure depends on the installed product, version, enabled functionality, and configuration. F5 disclosure index

Five receive F5 CVSS v4.0 scores of 9.2, Critical: CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, and CVE-2026-113425. Remote code execution remains a conditional impact.

Public research demonstrates CVE-2026-123007 exploitation in a controlled environment. As of November 19, 2026, no exploitation in the wild was confirmed in the sources reviewed. A public PoC or research demonstration does not establish operational exploitation.

Vulnerability summary

10Disclosed vulnerabilities
5Rated Critical by F5
November 18, 2026Public disclosure

The scores below are F5 CVSS v4.0 base scores for NGINX Open Source and Plus, obtained from F5 advisories or F5-authored CVE records. Citation limitations for three records are identified in the editorial note.

CVE Affected component Root-cause category Documented impact CVSS v4.0 — F5 Essential exposure conditions
CVE-2026-123007 HTTP/2 flow control Integer underflow and heap memory corruption Worker crash, memory corruption; potential RCE 9.2 Critical HTTP/2 enabled
CVE-2026-123633 HTTP/2 proxy processing Use-after-free DoS; potential code execution 9.2 Critical HTTP/2 client connections, backend proxying, insufficient available worker connections
CVE-2026-121810 HTTP/3 and QUIC Use-after-free Worker restart/DoS; potential code execution 9.2 Critical HTTP/3 enabled; connection-resource and additional runtime conditions
CVE-2026-118899 HTTP request-body processing Infinite loop Worker stops processing connections; DoS 8.7 High SSL-enabled HTTP listener using TLS 1.3
CVE-2026-120967 Stream TLS authentication Incorrect certificate-verification context Client-certificate verification bypass 6.3 Medium Client verification required in a non-default stream virtual server on a shared socket
CVE-2026-120993 Stream TLS handshake processing NULL pointer dereference Worker termination/DoS 6.9 Medium Dynamic certificates, stream proxying, outgoing PROXY protocol v2, abbreviated handshake
CVE-2026-123640 Stream TLS preread Inconsistent ClientHello interpretation Routing segmentation bypass; potential sensitive-backend access 6.9 Medium Routing restrictions depend on TLS preread values
CVE-2026-123634 DNS resolver and subrequests Use-after-free Worker crash, memory corruption; potential RCE 9.2 Critical Variable-based proxy destination and SSI/mirror subrequests resolving the same name
CVE-2026-113425 Mail proxy Use-after-free Worker crash, memory corruption; potential RCE 9.2 Critical Mail proxy functionality; documented research path uses HTTP authentication
CVE-2026-125283 Filesystem-path and capture processing Integer underflow/buffer overflow Worker termination/DoS 6.9 Medium Specific combinations of map variables, try_files, alias, and regex captures

These abbreviated conditions do not replace the full advisories. NGINX’s classifications—such as major, medium, and minor—are separate from CVSS ratings. For example, NGINX labels CVE-2026-123633 “medium,” while F5 assigns it Critical under CVSS v4.0. NGINX advisory index, F5 HTTP/2 advisory

Technical analysis

1. HTTP/2 and HTTP/3

CVE-2026-123007 — HTTP/2 flow-control memory corruption. Incorrect accounting allows the connection’s send window to exceed its permitted limit. Subsequent arithmetic and response-buffer handling can produce out-of-bounds memory access, worker crashes, and potential RCE. Exposure requires HTTP/2 to be enabled. F5 advisory

CVE-2026-123633 — HTTP/2 use-after-free. When a worker proxies HTTP/2 requests while running short of available connections, connection cleanup can leave processing dependent on released state. The result can be DoS or potential code execution. Enabling HTTP/2 alone does not establish the complete exposure conditions. F5 advisory

CVE-2026-121810 — HTTP/3 use-after-free. HTTP/3 connection and stream processing can access freed memory. Release information identifies insufficient worker connections as a relevant condition; F5 also notes dependencies beyond the attacker’s control. F5 advisory, Plus release history

For these three issues, and the resolver and mail flaws below, F5 qualifies code execution on ASLR being disabled or bypassed. Initial execution has the affected worker’s privileges. Worker-context RCE does not automatically provide root privileges, container escape, or host control.

2. HTTP request-body processing over TLS 1.3

CVE-2026-118899 can trap a worker in an infinite loop while it reads an HTTP request body over a crafted TLS connection. The worker stops accepting new connections and processing existing ones. The affected configuration requires an SSL-enabled HTTP listener using TLS 1.3; the stream module is not required. F5 advisory

3. Stream TLS authentication, handshake processing, and routing

CVE-2026-120967 — client-certificate verification bypass. Under the affected handshake conditions, verification can use the shared socket’s default-server configuration rather than the SNI-selected virtual server’s requirements. A connection may therefore bypass the intended client-certificate check. F5 excludes configurations where the default server already requires client verification. F5 advisory

CVE-2026-120993 — handshake-related worker termination. An abbreviated TLS handshake can encounter a NULL pointer when dynamic certificate loading interacts with stream proxying and outgoing PROXY protocol v2. The documented impact is DoS. F5 excludes builds using BoringSSL or AWS-LC. F5 advisory

CVE-2026-123640 — TLS preread routing bypass. Malformed ClientHello information can produce incorrect preread values or interpretation differences between NGINX and the backend TLS implementation. Where routing restrictions depend on those values, a connection may reach an otherwise restricted backend. This establishes a routing-control failure, not compromise of that backend. NGINX release notes

4. DNS resolver and subrequests

CVE-2026-123634 affects resolver lifetime handling when a variable-based proxy destination and an SSI or mirror subrequest resolve the same server name. Access to released memory can cause worker crashes, memory corruption, or conditional RCE. DNS resolution alone does not establish exposure. F5 advisory

5. Mail proxy authentication

CVE-2026-113425 affects mail proxy memory handling. The documented research path involves HTTP authentication: client-session cleanup can leave authentication processing referencing freed session memory. Worker crashes and memory corruption are documented impacts, with RCE conditional on ASLR being absent or bypassed. Ordinary HTTP reverse proxying does not meet this mail-specific exposure condition.

6. map, try_files, alias, and regex captures

CVE-2026-125283 involves particular capture interactions when try_files and alias use a map variable. Incorrect length handling can produce a buffer overflow and worker termination. The documented impact is DoS; finding one of these directives alone is insufficient to establish exposure. NGINX release notes

The findings have different discovery credits. NGINX’s change log acknowledges Xint.io, Albert of Vexera AI, Maxim Dounin, CERT.PL, ruokeqx, Vivek Parikh of BreachX Zero Day Labs, and Marc Luchian and Liviu-Alexandru Bud against individual CVEs. F5 additionally acknowledges independent reporters for the HTTP/2 findings. These acknowledgments should not be interpreted as a shared discovery date. NGINX change log, F5 flow-control advisory, F5 HTTP/2 use-after-free advisory

Exploit maturity and proof of concept

CVE-2026-123007

Stephen Fewer’s Rapid7 disclosure on November 18, 2026 accompanied public PoC code. The research demonstrates the flow-control flaw and unauthenticated RCE against NGINX 1.31.8 in a Linux/amd64 Docker environment with HTTP/2 over TLS.

The demonstrated strategy depends on a particular x86-64 glibc memory-copy implementation, a suitable initial heap state, substantial traffic volume, sufficient bandwidth within connection timeouts, and HTTP/2 traffic reaching the target without disruptive intermediary processing. It includes address disclosure to overcome ASLR.

These are constraints of the published technique, not universal prerequisites for every possible exploitation method.

Other public research

Exploit evidence differs by CVE:

CVE Evidence reviewed
CVE-2026-123633 Xint reports RCE validation; a separate public repository claims PoC coverage
CVE-2026-121810 Xint reports RCE validation; a third-party repository claims a Docker PoC
CVE-2026-118899 A third-party repository claims a TLS 1.3 DoS PoC
CVE-2026-123634 Xint reports RCE validation; a third-party repository claims a resolver/subrequest crash demonstration
CVE-2026-113425 Xint reports RCE validation; a third-party repository claims a mail-authentication crash demonstration

Repository claims do not establish functional or reliable exploitation. Reviewed repositories for CVE-2026-120967 and CVE-2026-125283 describe their PoCs as work in progress. A repository claiming CVE-2026-123640 coverage misidentifies the issue as HTTP/3 use-after-free and does not establish a valid PoC.

Reproducibility and reliability: Not independently tested. No exploit was reproduced for this article. Research and repository links are omitted under the approved-domain policy; the resulting citation gap is identified after the article.

Timeline and disclosure-to-PoC timing

  1. October 14, 2026CVE-2026-123633 and CVE-2026-123640

    Plus fixes shipped in PLS.37.0.7.1 LTS and PLS.37.2.0.1 CR

  2. November 11, 2026CVE-2026-123007

    Rapid7 reports initial outreach to F5

  3. November 12, 2026CVE-2026-123007

    Rapid7 reports technical disclosure and acknowledgment

  4. November 16, 2026CVE-2026-123007

    Rapid7 reports F5 validation, CVE assignment, and disclosure-date confirmation

  5. November 18, 2026All ten

    F5 disclosure; Open Source 1.30.7 stable and 1.31.9 mainline released

  6. November 18, 2026Applicable Plus disclosure set

    PLS.37.0.8.1 LTS and PLS.37.3.0.1 CR released

  7. November 18, 2026CVE-2026-123007

    Rapid7 research published with accompanying public PoC

Vendor dates are supported by the NGINX release announcement and Plus release history. Rapid7-specific events are researcher-reported.

CVE-2026-123007 disclosure and public PoC publication occurred on the same calendar day. This establishes zero calendar days between them, not an exact hourly interval. It does not establish time to exploitation in the wild.

Researcher-demonstrated vulnerability chaining

Xint reports combining CVE-2026-123007 worker-context RCE with a separate Linux SCTP kernel privilege-escalation flaw to obtain host root access from a containerized deployment.

Research chain: separate vulnerabilities

This is a research demonstration, not evidence of an active attack campaign. The chain was not reproduced for this article, and reviewed approved-domain sources do not substantiate its operational details. The NGINX vulnerability alone must not be described as providing root access or container escape.

Affected versions and security updates

Product or track Upgrade target at the reporting cutoff
NGINX Open Source stable 1.30.7
NGINX Open Source mainline 1.31.9
NGINX Plus Long-Term Support PLS.37.0.8.1 LTS
NGINX Plus Continuous Release PLS.37.3.0.1 CR

The Open Source releases were announced on November 18, 2026. Use the appropriate fixed branch or a later supported release containing the applicable fixes. NGINX announcement

Earlier Plus releases PLS.37.0.7.1 LTS and PLS.37.2.0.1 CR already fixed CVE-2026-123633 and CVE-2026-123640 on October 14. They do not cover the complete applicable November disclosure set. CVE-2026-120993 is listed among the new CR’s fixes and should not be assumed to affect every Plus track. Plus release history

For older Plus branches, follow the individual advisory: where no in-branch fix is listed, migrate to a release containing the fix. Embedded products require their own product/package guidance.

Official-source differences

For CVE-2026-120993, NGINX lists affected mainline versions 1.31.4–1.31.8, fixed in 1.31.9. F5 lists 1.31.0–1.31.8. On stable, F5 identifies 1.30.6 as affected and 1.30.7 as fixed, while NGINX’s corresponding index entry omits both. These differences remain unresolved. NGINX advisory index, F5 advisory

For CVE-2026-118899, the retrieved F5 table lists Open Source 1.13.0 without a fix, while NGINX’s index and announcement identify a broader affected range and the November fixed releases. This is an advisory-table inconsistency, not evidence that upstream fixes are unavailable. F5 advisory, NGINX announcement

Verify the package, not just the version banner

Distribution vendors may backport fixes while retaining an older upstream version. Verify the complete package release and vendor fix evidence, rather than relying on the server banner.

Temporary exposure reduction

Mitigation does not replace patching. Test changes against clients, upstream services, authentication requirements, and routing behavior.

CVE Temporary measure and qualification
CVE-2026-123007 and CVE-2026-123633 Disable HTTP/2 to remove the affected client-protocol path. This is exposure-reduction guidance; the reviewed F5 advisories list no mitigation
CVE-2026-121810 Disable HTTP/3 and its QUIC listeners to remove the affected processing path. Client-compatibility testing is required; F5 lists no mitigation
CVE-2026-120967 Require client verification in the shared socket’s default stream server, or move the protected virtual server to a dedicated listening address and port
CVE-2026-120993 Disable outgoing PROXY protocol v2, use compatible v1 instead, or disable abbreviated handshakes through both session-ticket and session-cache changes
CVE-2026-123640 Replace affected preread routing with TLS termination at NGINX where operationally appropriate
CVE-2026-123634 Avoid the affected SSI/mirror and variable-based proxy configuration
CVE-2026-113425 Restrict mail listeners to trusted networks
CVE-2026-125283 Use named regex captures instead of unnamed captures; do not reuse capture variables in other regex matches or for unrelated purposes

The stream-authentication, handshake, and resolver measures are documented in the respective authentication advisory, handshake advisory, and resolver advisory. The preread, mail, and capture recommendations were verified in F5-authored CVE records.

Routing changes require security validation

TLS termination changes where encryption ends. For CVE-2026-123640, validate certificate/key management, upstream TLS requirements and verification, and backend selection. Simply disabling preread without redesigning dependent routing is insufficient.

F5 lists no mitigation for CVE-2026-118899; prioritize the applicable update. F5 advisory

These recommendations are distinct from distribution-specific guidance. Ensure old connections and workers no longer retain the affected processing path after changes are activated.

Detection and remediation priorities

Exposure assessment flow

  1. Affected package or image?
    Match the complete installed release and running image to vendor guidance, including distribution backports. If unknown, resolve the inventory gap before closing the finding.
  2. Relevant functionality enabled and reachable?
    Check the full advisory conditions for HTTP/2, HTTP/3, TLS 1.3, stream, resolver, mail, or filesystem routing. If the path is absent, record that finding and still plan applicable updates.
  3. Critical service or security boundary exposed?
    Prioritize internet-facing services, authentication and routing controls, and availability-critical workloads. Apply tested temporary controls when an immediate update is not possible.
  4. Fixed software running and validated?
    Update → replace outdated processes → test service and security behavior → rescan. Keep remediation open while any required check remains unresolved.

Prioritize reachable vulnerable functionality, particularly internet-facing HTTP/2 services given the public CVE-2026-123007 demonstration. Also assess exposed stream authentication and routing boundaries, HTTP/3 proxies, resolver/subrequest combinations, mail proxies, and availability-critical TLS 1.3 services.

Review configured HTTP, stream, and mail logs; NGINX error logs; service and container restart records; crash reports; network telemetry; and endpoint process activity. Investigate unexpected worker exits, sustained resource exhaustion, unusual connection volumes, authentication anomalies, incorrect backend selection, and unexplained programs started by workers.

These are investigation signals rather than validated CVE-specific IOCs. Worker crashes are nonspecific and do not prove compromise. HTTP access logs may not capture protocol-level activity, and absence of crashes does not establish patch status.

Post-remediation validation

From discovery to verified remediation

STEP 1
Inventory

Identify the product, complete package or image, and enabled functionality.

STEP 2
Assess exposure

Match reachable service paths and configuration to each advisory.

STEP 3
Update

Deploy the applicable fixed release or vendor-backed package.

STEP 4
Activate

Restart, replace instances, or use a supported executable upgrade.

STEP 5
Validate

Check running processes, service behavior, security controls, and scan results.

  1. Confirm the fixed software is deployed. Match the complete installed package or image to applicable vendor fix evidence. Account for distribution backports. In containerized deployments, verify the running image identity and successful rollout across every container and replica.
  2. Confirm the fixed executable is running. Establish that the active service uses the updated executable and that outdated master and worker processes have exited. Checking installed files does not prove running-process status. A configuration reload alone does not replace the executable; use a restart, instance replacement, or supported executable upgrade as appropriate. NGINX process control
  3. Validate and activate the intended configuration. Use the service’s actual executable and configuration inputs. Confirm successful activation through service logs and functional checks rather than relying only on files saved to disk.
  4. Test the affected service paths. Confirm intended HTTP/2 or HTTP/3 negotiation without mistaking fallback for success. Exercise TLS 1.3 request bodies and relevant proxy, resolver/subrequest, mail, and filesystem-routing functions.
  5. Verify security controls. Confirm authorized clients succeed and unauthorized clients are rejected. Check intended backend selection, restricted-destination isolation, and proxy behavior. Where TLS or PROXY protocol changed, verify certificates, upstream TLS expectations, and connection metadata.
  6. Review logs and rescan. Investigate unexpected crashes, TLS failures, authentication errors, and upstream failures. Run updated authenticated scans. Confirm previous findings clear or reconcile residual findings individually against package versions, vendor evidence, and scanner logic.

Functional checks supplement patch verification; they do not independently prove the absence of memory-corruption defects.

Conclusion

The November NGINX disclosures require configuration-aware remediation. These ten vulnerabilities affect different processing paths, so priority should reflect the installed release, enabled features, and reachable services. Internet-facing HTTP/2 services warrant particular attention given the public CVE-2026-123007 demonstration, alongside exposed authentication, routing, and availability-critical functions.

Public proof-of-concept research increases the urgency to act, but it does not establish exploitation in the wild. At the November 19, 2026 research cutoff, the reviewed sources did not confirm active exploitation. Conditional worker-context code execution also should not be treated as automatic root access or container escape.

Deploy the applicable fixed release or vendor-backed package, ensure updated executables are running across every instance and replica, and validate the affected service paths and security controls. Temporary configuration changes can reduce exposure, but they do not replace patching.

References

  1. F5 November 18, 2026 disclosure index, linking the individual advisories.
  2. NGINX security advisory index.
  3. NGINX release announcements and change log.
  4. NGINX Plus release history.
  5. NGINX process control.

Instantly Fix Risks in Endpoints & Cloud with Saner

Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.

Schedule a Demo

Featured Posts

Open ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access
ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access

CVE Research

ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access

CVE-2026-126755 is a critical ArangoDB authentication bypass vulnerability affecting versions before 3.12.11. Learn how inconsistent URL parsing can enable unauthenticated superuser access, its security impact, and recommended detection and remediation measures.

Nov 19, 2026

Open Critical Apache Roller RCE Vulnerability CVE-2026-129448 Exploited in Active Attacks
threat intelligenceCritical Apache Roller RCE Vulnerability CVE-2026-129448 Exploited in Active Attacks

CVE Research

Critical Apache Roller RCE Vulnerability CVE-2026-129448 Exploited in Active Attacks

Apache Roller CVE-2026-129448, a critical vulnerability with a CVSS score of 9.8, is under active exploitation. The flaw allows unauthenticated remote code execution through insecure XML-RPC deserialization, affecting Apache Roller versions 4.0.0 through 6.1.5. Explore the technical details, exploitation risks, and recommended fixes.

Nov 19, 2026

Open BO Team Weaponizes Log4Shell to Turn VMware Infrastructure Into a Supply Chain Launchpad
BO Team Weaponizes Log4Shell to Turn VMware Infrastructure Into a Supply Chain Launchpad

CVE Research

BO Team Weaponizes Log4Shell to Turn VMware Infrastructure Into a Supply Chain Launchpad

Nov 19, 2026

Open Six Critical F5 BIG-IP Vulnerabilities Expose Systems to Remote Code Execution and DoS Attacks
vulnerability researchSix Critical F5 BIG-IP Vulnerabilities Expose Systems to Remote Code Execution and DoS Attacks

CVE Research

Six Critical F5 BIG-IP Vulnerabilities Expose Systems to Remote Code Execution and DoS Attacks

F5 has disclosed six critical BIG-IP vulnerabilities, each rated CVSS 9.8, that could allow unauthenticated attackers to crash the Traffic Management Microkernel (TMM) and potentially execute remote code. Learn about the affected products, exploitation conditions, security risks, and available engineering hotfixes.

Nov 19, 2026