Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2026-57024


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.


Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.3, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and limited availability for affected systems. Impacting 24 products from juniper, from juniper, from juniper and 21 others, organizations running these solutions should prioritize assessment and patching.

Historical Context

Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.


Published

2026-07-09T22:17:07.553

Last Modified

2026-07-14T15:16:42.397

Status

Analyzed

Source

[email protected]

Severity

CVSSv3.1: 5.3 (MEDIUM)

Weaknesses
  • Type: Secondary
    CWE-694

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Operating System juniper junos < 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.2 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 23.4 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.2 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 24.4 Yes
Operating System juniper junos 25.2 Yes
Operating System juniper junos 25.2 Yes
Hardware juniper mx-spc3 - No
Hardware juniper mx240 - No
Hardware juniper mx480 - No
Hardware juniper mx960 - No
Hardware juniper srx1500 - No
Hardware juniper srx1600 - No
Hardware juniper srx2300 - No
Hardware juniper srx300 - No
Hardware juniper srx320 - No
Hardware juniper srx340 - No
Hardware juniper srx345 - No
Hardware juniper srx380 - No
Hardware juniper srx400 - No
Hardware juniper srx4100 - No
Hardware juniper srx4120 - No
Hardware juniper srx4200 - No
Hardware juniper srx4300 - No
Hardware juniper srx440 - No
Hardware juniper srx4600 - No
Hardware juniper srx4700 - No
Hardware juniper srx5400 - No
Hardware juniper srx5600 - No
Hardware juniper srx5800 - No

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.