Skip to content
Brief Security & Trust ·

F5 and Juniper patch critical flaws, SecurityWeek reports

SecurityWeek says both vendors fixed dozens of bugs, with no attacks in the wild mentioned.

In brief
  • F5 fixed 11 NGINX flaws, three critical. Juniper issued 17 advisories covering over 150 Junos flaws, about two dozen critical.
  • For NGINX, ASLR is what separates a crash from code execution.

F5 said on October 14, 2026 that it had published new security notices. SecurityWeek reported on October 16 that F5 fixed 11 NGINX flaws, three critical: CVE-2026-15176, CVE-2026-93479 and CVE-2026-97205. It said Juniper Networks issued 17 advisories covering over 150 flaws in Junos OS and Junos OS Evolved, plus four in Cloud-Native Router. About two dozen are critical.

F5's page is only an index that points to separate articles. SecurityWeek says the first two NGINX flaws can be hit without logging in, using crafted web requests, under conditions beyond the attacker's control. A buffer overflow is a program writing more data than a space can hold. Here it can force a restart. If ASLR, which randomizes where data sits in memory, is disabled or can be bypassed, an attacker could run code. SecurityWeek says Juniper's critical flaws include root-level command execution, full device takeover and an off-by-one overflow. Neither vendor mentions attacks in the wild. The reports give no fix versions and name no Juniper critical flaws.

In the NGINX flaws, ASLR is what separates a crash from code execution. Leaders can ask where NGINX and Junos run, who owns patching, and whether ASLR is on. Juniper's critical details come only from SecurityWeek's summary.

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: F5, Inc., CrowdStrike.