Juniper patches 160+ Junos OS flaws
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
CERT-FR advisory covers over 150 Juniper Networks vulnerabilities in Junos OS, Junos OS Evolved and Cloud-Native Router, including remote code execution and DoS flaws.
CERT-FR has published a consolidated advisory relaying Juniper Networks' October 2026 security bulletins, covering a very large batch of vulnerabilities across Junos OS, Junos OS Evolved, and the Juniper Cloud-Native Router. Affected platforms include MX Series, SRX Series (standalone and with SPC3), and Cloud-Native Router deployments across numerous version branches from 23.2 through 26.2. The flaws span remote code execution, privilege escalation, remote denial of service, data integrity and confidentiality breaches, security policy bypass, and SQL injection.
Notable individually documented issues include a remote code execution flaw triggered by a malformed ADVPN peer message on SRX Series (CVE-2026-102084), a command injection vulnerability caused by missing authorization on certain CLI request commands on MX Series (CVE-2026-102079), and an inadvertently exposed port reachable by an attacker on Junos OS Evolved (CVE-2026-102085). Multiple denial-of-service conditions were also disclosed: rpd crashes from crafted BGP-LS attributes in traffic-engineering scenarios, flowd crashes from DNS queries processed by SecIntel/DGA detection or high-volume DNS-over-TCP traffic, PFE crashes from malformed TLS session resumption messages, continuous RE switchover from malformed SyncE/PTP clock input, and memory/resource leaks from high session churn or malformed NAT packet handling.
Juniper has released fixed versions for each affected branch; no evidence of in-the-wild exploitation is noted in the advisory. Defenders running any of the listed Junos OS, Junos OS Evolved, or Cloud-Native Router versions should prioritize patching MX and SRX Series devices exposed to untrusted traffic, particularly those using ADVPN, WebFiltering, SecIntel/DGA, or TLS session resumption features, and should review CLI command authorization configurations.
Mentioned in this report
Source reporting: https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1322
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs