Impacts widely deployed Juniper SRX enterprise firewalls; allows remote code execution and full device takeover, risking major network/infrastructure disruption.
CVE-2026-102084
Buffer overflow in Juniper SRX ADVPN allows remote takeover of devices.
Is CVE-2026-102084 being exploited?
Not confirmed. CVE-2026-102084 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-102084?
CVE-2026-102084 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102084?
Yes. A fix has been recorded for CVE-2026-102084. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102084 affect?
CVE-2026-102084 affects Juniper SRX Series (Junos OS < 23.2R2-S7.7), Junos OS 23.4 before 23.4R2-S7, Junos OS 24.2 before 24.2R2-S4, Junos OS 24.4 before 24.4R2-S3, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102084?
Apply vendor patches immediately; restrict ADVPN peers and rotate shared secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via malformed ADVPN attributes leading to full device compromise if attacker can impersonate a peer (requires shared secret).
Immediate action required
- affected< 23.2R2-S7.7
- affected>= 23.4 and < 23.4R2-S7
- affected>= 24.2 and < 24.2R2-S4
- affected>= 24.4 and < 24.4R2-S3
- affected>= 25.2 and < 25.2R2
- affected>= 25.4 and < 25.4R1-S3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.