CVE-2026-57024

Awaiting Analysis Awaiting Analysis - Queue

DoS in Juniper Junos OS iked VPN Service

Publication date: 2026-07-09

Last updated on: 2026-07-10

Assigner: Juniper Networks, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-09

Last Modified

2026-07-10

Generated

2026-07-11

AI Q&A

2026-07-10

EPSS Evaluated

N/A

NVD

CVE-2026-57024

EUVD

EUVD-2026-42712

Affected Vendors & Products

Vendor	Product	Version / Range
juniper_networks	junos_os	to 23.2R2-S7 (exc)
juniper_networks	junos_os	to 23.4R2-S6 (exc)
juniper_networks	junos_os	to 24.2R2-S3 (exc)
juniper_networks	junos_os	to 24.4R2-S4 (exc)
juniper_networks	junos_os	to 25.2R1-S1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-694	The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.

Attack-Flow Graph

Executive Summary

This vulnerability is a Use of Multiple Resources with Duplicate Identifier issue in the IKE daemon (iked) of Juniper Networks Junos OS on MX with SPC3 and SRX Series devices. It allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS) condition.

The problem occurs when many VPN negotiations fail, causing a peer index rollover. New peers are then assigned index values that are already in use, which causes the iked process to crash repeatedly. This crash prevents the establishment of new VPN connections and the rekeying of existing ones, requiring a system reboot to restore service.

The vulnerability affects systems running the iked process (not kmd) on specific Junos OS versions before certain patches.

Impact Analysis

This vulnerability can cause a Denial-of-Service (DoS) on affected Juniper devices, disrupting VPN services.

Specifically, the iked process crashes repeatedly, preventing new VPN connections from being established and stopping existing VPN tunnels from rekeying.

As a result, network connectivity relying on VPNs may be interrupted until the device is rebooted to restore service.

Detection Guidance

This vulnerability can be detected by monitoring tunnel up and down events over an extended period of time, as the index value causing the issue cannot be directly monitored.

To verify if the system is running the affected iked process (and not the unaffected kmd), you can use the following command:

show system processes extensive | match "KMD|IKED"

If many VPN negotiation failures and tunnel flaps are observed, it is likely that this vulnerability is being triggered.

Mitigation Strategies

Immediate mitigation involves monitoring VPN tunnel stability and reducing the number of failed VPN negotiations to prevent peer index rollover.

If the iked process crashes and VPN connections fail, the system must be rebooted to restore service.

Additionally, ensure that your Junos OS version is updated to a fixed release version, such as 23.2R2-S7 or later, 23.4R2-S6 or later, 24.2R2-S3 or later, 24.4R2-S4 or later, or 25.2R1-S1 or later, to permanently address the vulnerability.

Hi! I’m here to help you understand CVE-2026-57024. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70