A newly described remote denial-of-service pattern shows how header compression and connection retention can turn HTTP/2 into a resource-exhaustion problem for major web stacks.
A reported “HTTP/2 Bomb” issue puts availability back in the spotlight, showing how default HTTP/2 handling can become a pressure point for major web servers and proxies.
A newly disclosed HTTP/2 issue may enable remote denial-of-service conditions against nginx, Apache httpd, Microsoft IIS, Envoy, and Cloudflare Pingora.
A new exploit label is drawing attention to a familiar problem: HTTP/2 efficiency features can become resource-pressure points when limits are too loose.
CVE-2026-9256 sits in a narrow but dangerous corner of NGINX: rewrite rules that reuse overlapping PCRE captures can push a worker into denial of service and, under added conditions, into remote code execution.
A memory-safety flaw in NGINX’s rewrite path shows how ordinary request parsing can turn into denial of service, and in narrower conditions, remote code execution.
A newly named flaw has put NGINX back in the spotlight, but the real story is how quickly an unverified RCE claim can pressure defenders at the edge of the internet.
A claimed remote code execution bug in NGINX 1.31.0 has raised attention, yet the public technical trail still lacks the kind of evidence defenders need before panic becomes policy.
A flaw in the njs extension shows how an edge feature built for flexibility can become a crash path - and, in some conditions, a route to code execution.
CVE-2026-8711 is a configuration-dependent heap overflow in NGINX JavaScript that can knock over worker processes and, in limited conditions, open the door to code execution.
A newly tracked NGINX bug, labeled “Nginx Rift” in one public account, shows how edge-proxy logic can turn into an availability problem when attackers hit the right request pattern.
A new wave of attacks around “Nginx Rift” shows how a web server can become dangerous not only because of its version, but because of the way it is configured.
A narrow configuration path in the rewrite module has pushed CVE-2026-42945 into urgent territory, where patching and config review now matter as much as uptime.
A configuration-sensitive flaw tied to CVE-2026-42945 shows how a familiar edge proxy feature can become a crash vector, and in some environments, a route to remote code execution.
A critical heap buffer overflow in NGINX’s rewrite path can crash worker processes and, under narrower conditions, may also create a path to remote code execution.
A critical flaw in NGINX’s request-rewrite path can crash workers on affected setups, and memory protections determine whether the danger stops at denial of service or climbs toward code execution.
A configuration-shaped memory bug in NGINX’s rewrite module turns routine URL logic into a high-severity exposure for servers that match the trigger pattern.
Public proof-of-concept code has sharpened attention on a critical NGINX flaw that lives in a configuration path many teams treat as routine.
A security notice about F5 updates has turned into a deeper infrastructure question: when a memory-corruption bug already has a public PoC, how quickly can edge teams prove they are safe?
A critical flaw in NGINX’s rewrite engine turns a routine configuration pattern into a memory-corruption risk for internet-facing proxies, load balancers, and ingress tiers.