Critical Buffer Overflow Vulnerability in nginx:1.26 - Remote Code Execution Risk

nginx Updated 10 Jul 2026

Summary

08/07/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:36639: Important: nginx:1.26 security, bug fix, and enhancement update. Affects nginx versions < 2:1.26.3-9.module_el9.8.0+281+75d5e6d4.2. Fixed in 2:1.26.3-9.module_el9.8.0+281+75d5e6d4.2. 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 Your last release was probably never penetration tested 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 high-performance web and proxy server that supports HTTP and other protocols, designed for high concurrency, performance, and low memory usage. It is widely used for serving static content, load balancing, and as a reverse proxy. The recent vulnerability affects nginx version 1.26, which could lead to severe security risks if not addressed promptly.

Vulnerability Detail

The vulnerability identified as CVE-2026-42055 is a heap-based buffer overflow that can be exploited through crafted HTTP/2 headers. This flaw allows attackers to execute arbitrary code or cause a Denial of Service (DoS), potentially compromising the server's integrity and availability. The issue arises from improper handling of HTTP/2 requests, making it critical for users to update their installations to mitigate risks.

How To Fix

Minimum fixed version

2:1.26.3-9.module_el9.8.0+281+75d5e6d4.2

This is the first release that contains the fix.

sudo dnf update nginx

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

Workaround

As a temporary workaround, users can disable HTTP/2 support in their nginx configuration until the update is applied. This can be done by modifying the nginx configuration file (usually located at /etc/nginx/nginx.conf) and removing or commenting out the 'http2' directive in the server block.

Conclusion

The nginx:1.26 vulnerability (CVE-2026-42055) poses a significant risk of arbitrary code execution and Denial of Service due to a heap-based buffer overflow. It is crucial for users to update their nginx installations to the patched version to ensure the security and stability of their web services.

See every vulnerability recorded for nginx →

Share this vulnerability

FAQ

CVE-2026-42055 is a critical vulnerability in nginx that allows for arbitrary code execution or Denial of Service via a heap-based buffer overflow caused by crafted HTTP/2 headers.

You can check your nginx version by running the command 'nginx -v' in your terminal. If your version is below 2:1.26.3-9.module_el9.8.0+281+75d5e6d4.2, it is vulnerable.

Failing to update nginx exposes your server to potential remote code execution and Denial of Service attacks, which can compromise your system's security and availability.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just a manifest file. You can check your application for vulnerabilities using the Vulert playground without any signup.

If immediate updating is not possible, consider disabling HTTP/2 support in your nginx configuration as a temporary measure to mitigate the risk until you can apply the patch.

Related vulnerabilities

Recent vulnerabilities recorded for nginx.

How To Fix

Minimum fixed version

2:1.26.3-9.module_el9.8.0+281+75d5e6d4.2

This is the first release that contains the fix.

sudo dnf update nginx

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