NGINX Security Release Fixes Five Remote-Code-Execution Flaws


F5 issued an out-of-band security notification November 18 covering multiple NGINX vulnerabilities. CERT-EU highlighted five configuration-dependent flaws that can allow an unauthenticated attacker to execute code with the privileges of an NGINX worker process.
NGINX Open Source 1.31.9 and 1.30.7 contain the relevant fixes. F5 lists fixed NGINX Plus releases by branch in its individual advisories. CERT-EU says researchers demonstrated CVE-2026-123007, but no exploitation in the wild had been reported when its advisory was published.
The reviewed evidence establishes vulnerable software paths and available fixes. It does not establish that a dealership, automotive vendor or customer system runs an affected configuration or has been compromised.
Priority flaws5Configuration-dependent code-execution paths
Open Source fixes1.31.9 / 1.30.7NGINX mainline and stable branches
Leading score8.1CVSS 3.1 for the five CERT-EU highlights
Known exploitationNone reportedCERT-EU, Nov. 18
Beyond automotive: what is confirmed
The five flaws involve different NGINX features. Two require HTTP/2; one requires HTTP/3 and upstream proxying; one requires a specific resolver, proxy and mirror configuration; and one involves the mail proxy module with external authentication. Their vulnerable version ranges differ, so a product name alone is not enough to determine exposure.
CVE-2026-123007 is the broadest of the five highlighted paths: NGINX lists Open Source 1.9.5 through 1.31.8 as vulnerable when HTTP/2 is enabled. F5 says exploitation can crash a worker, corrupt memory or potentially execute code remotely. NGINX lists 1.31.9 and 1.30.7 as non-vulnerable releases for the affected open-source branches.
Why it matters
NGINX can sit in front of websites, APIs and hosted applications, but DTR has not established which dealership or automotive systems use it. The practical dealership control is vendor accountability: the party operating each internet-facing service should be able to identify the web-server product and version, determine whether the affected feature is enabled and document the fixed release or supported mitigation.
A generic statement that a service is cloud hosted does not answer the exposure question. At the same time, the advisory is not evidence that every NGINX system is vulnerable or that an incident occurred. Configuration and version evidence are required.
What dealerships and technology providers should do
Prioritize public websites, APIs, portals and remote-access services. Ask the responsible provider whether NGINX is in the request path, which version and branch is running, which affected modules are enabled, and when the fixed release was deployed. Self-managed NGINX Open Source systems should be matched to the official advisory and updated through the normal tested change process.
CERT-EU says disabling HTTP/2 on exposed listeners can mitigate CVE-2026-123007 and CVE-2026-123633 when an immediate update is not possible. That change can affect application behavior and performance, so it belongs with the responsible administrator or vendor—not an unsupported dealership-side workaround. Worker crashes may indicate an attempt but are not proof of successful code execution; suspicious activity requires broader log and process review.
AI-assisted reporting disclosure
This article was researched and generated with AI-assisted systems using the F5, NGINX and CERT-EU sources listed below. Dealership Tech Report applies automated accuracy, attribution and risk checks. Vulnerability, version, exploitation and mitigation statements remain attributed to the named authorities; dealership actions are editorial recommendations, not a finding that an automotive system is affected.
This article reflects F5, NGINX and CERT-EU advisories checked November 19, 2026. The flaws have different prerequisites and version ranges. CERT-EU reported no known exploitation in the wild at publication, but that status can change. The reviewed sources do not establish that any dealership or automotive vendor uses an affected configuration or has been compromised. Providers should use the current vendor advisory for their exact product and branch.
Cited references
- F5 — Out-of-band Security Notification, November 18, 2026 — Primary vendor security-notification index; published Nov. 18, 2026
- NGINX — Security advisories — Primary vendor version and fix matrix; checked Nov. 19, 2026
- CERT-EU — Critical vulnerabilities in Nginx — National CERT advisory; published Nov. 18, 2026