CVE-2026-57024

Junos OS: MX with SPC3, SRX Series: Repeated VPN negotiation failures will eventually cause iked to crash continuously

MEDIUM

5.3

CVSS Score

Published: July 9, 2026 at 09:06 PM UTC

Updated: October 25, 2026 at 03:10 PM UTC

1 product affected across 1 vendorJunos· also runs on 23 platforms

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 0.4%

SSVC

No known exploit

Description

A Use of Multiple Resources with Duplicate Identifier vulnerability in the IKE daemon (iked) of Juniper Networks Junos OS on MX with SPC3 and SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). On an MX with SPC3 and SRX devices configured for VPN service, when a large number of VPN negotiations fail a peer index rollover will eventually occur. As a result, new peers are assigned index values that are already in use and the iked process starts to crash repeatedly. This results in failure to establish new VPN connections and rekeying existing ones. To restore service the system must be rebooted. Please note that the index value can't be monitored, so customers should monitor tunnel up and down events and if a lot of events occur over an extended period of time it becomes likely that this issue occurs. To be exposed to this issue the system needs to run iked (vs. kmd which is not affected), which can be verified with: user@host> show system processes extensive | match "KMD|IKED" This issue affects Junos OS on MX with SPC3, SRX Series: * all versions before 23.2R2-S7, * 23.4 versions before 23.4R2-S6, * 24.2 versions before 24.2R2-S3, * 24.4 versions before 24.4R2-S4, * 25.2 versions before 25.2R1-S1.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos · Juniper Networks

95%

Affected range stops below 23.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 23.2R2-S7, so it looks safe — our inference, not a vendor statement

Affected range stops below 23.4R2-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 24.2R2-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 24.4R2-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 25.2R1-S1, so it looks safe — our inference, not a vendor statement

juniper-mx-spc3 (environment) · juniper-mx240 (environment) · juniper-mx480 (environment) · juniper-mx960 (environment) · juniper-srx1500 (environment) · juniper-srx1600 (environment) · juniper-srx2300 (environment) · juniper-srx300 (environment) · juniper-srx320 (environment) · juniper-srx340 (environment) · juniper-srx345 (environment) · juniper-srx380 (environment) · juniper-srx400 (environment) · juniper-srx4100 (environment) · juniper-srx4120 (environment) · juniper-srx4200 (environment) · juniper-srx4300 (environment) · juniper-srx440 (environment) · juniper-srx4600 (environment) · juniper-srx4700 (environment) · juniper-srx5400 (environment) · juniper-srx5600 (environment) · juniper-srx5800 (environment)