Critical Vulnerability in nginx:1.26 - Arbitrary Code Execution Risk

nginx-all-modules Updated 26 May 2026

Summary

19/05/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:19372: Critical: nginx:1.26 security update. Affects nginx-all-modules versions < 2:1.26.3-9.module_el9.8.0+247+aa936373. Fixed in 2:1.26.3-9.module_el9.8.0+247+aa936373. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

nginx is a widely used web and proxy server known for its high concurrency, performance, and low memory usage. It supports various protocols, including HTTP, and is often employed to serve static content and as a reverse proxy. This particular version, nginx:1.26, has been identified with a critical security vulnerability that could allow attackers to execute arbitrary code, posing significant risks to server integrity and data security.

Vulnerability Detail

The vulnerability identified as CVE-2026-42945 allows for arbitrary code execution within the nginx server. This issue arises from improper handling of certain requests, which can be exploited by an attacker to execute malicious code on the server. The ramifications of this vulnerability are severe, as it could lead to unauthorized access, data breaches, and complete server compromise, making it critical for users to address it promptly.

How To Fix

Minimum fixed version

2:1.26.3-9.module_el9.8.0+247+aa936373

This is the first release that contains the fix.

sudo dnf update nginx-all-modules

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can restrict access to the nginx server by implementing firewall rules or modifying the server configuration to limit exposure to untrusted networks. However, this is not a permanent solution and should only be used until the patch is applied.

Conclusion

The nginx:1.26 vulnerability (CVE-2026-42945) poses a significant risk due to its potential for arbitrary code execution. It is crucial for users to update their nginx packages to the latest patched version to mitigate this risk. Additionally, employing temporary workarounds can help protect systems until the update is applied.

See every vulnerability recorded for nginx-all-modules →

Share this vulnerability

FAQ

CVE-2026-42945 is a critical vulnerability in nginx that allows for arbitrary code execution, potentially compromising server security.

You can use tools like Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

The risks include unauthorized access, data breaches, and potential complete server compromise, which can lead to significant operational and reputational damage.

You can update your nginx packages by running 'sudo dnf update nginx-all-modules nginx-filesystem' in your terminal, followed by restarting the nginx service.

Yes, you can temporarily restrict access to your nginx server using firewall rules or adjusting server configurations to limit exposure.

Related vulnerabilities

Recent vulnerabilities recorded for nginx-all-modules.

How To Fix

Minimum fixed version

2:1.26.3-9.module_el9.8.0+247+aa936373

This is the first release that contains the fix.

sudo dnf update nginx-all-modules

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback