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

Published Jul 9, 2026
·
Updated

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 Software

67 affected components
Juniper Networks Junos OS (MX with SPC3, SRX Series) - iked<23.2R2-S7
Juniper Networks Junos OS (MX with SPC3, SRX Series) - iked<23.4R2-S6
Juniper Networks Junos OS (MX with SPC3, SRX Series) - iked<24.2R2-S3
Juniper Networks Junos OS (MX with SPC3, SRX Series) - iked<24.4R2-S4
Juniper Networks Junos OS (MX with SPC3, SRX Series) - iked<25.2R1-S1
All of the following
Any of the following
Juniper Junos<23.2
Juniper Junos=23.2
Juniper Junos=23.2-r1
Juniper Junos=23.2-r1-s1
Juniper Junos=23.2-r1-s2
Juniper Junos=23.2-r2
Juniper Junos=23.2-r2-s1
Juniper Junos=23.2-r2-s2
Juniper Junos=23.2-r2-s3
Juniper Junos=23.2-r2-s4
Juniper Junos=23.2-r2-s5
Juniper Junos=23.2-r2-s6
Juniper Junos=23.4
Juniper Junos=23.4-r1
Juniper Junos=23.4-r1-s1
Juniper Junos=23.4-r1-s2
Juniper Junos=23.4-r2
Juniper Junos=23.4-r2-s1
Juniper Junos=23.4-r2-s2
Juniper Junos=23.4-r2-s3
Juniper Junos=23.4-r2-s4
Juniper Junos=23.4-r2-s5
Juniper Junos=24.2
Juniper Junos=24.2-r1
Juniper Junos=24.2-r1-s1
Juniper Junos=24.2-r1-s2
Juniper Junos=24.2-r2
Juniper Junos=24.2-r2-s1
Juniper Junos=24.2-r2-s2
Juniper Junos=24.4
Juniper Junos=24.4-r1
Juniper Junos=24.4-r1-s2
Juniper Junos=24.4-r1-s3
Juniper Junos=24.4-r2
Juniper Junos=24.4-r2-s1
Juniper Junos=24.4-r2-s2
Juniper Junos=24.4-r2-s3
Juniper Junos=25.2
Juniper Junos=25.2-r1
Any of the following
Juniper MX-SPC3
Juniper MX240
Juniper MX480
Juniper MX960
Juniper SRX1500
Juniper SRX1600
Juniper SRX2300
Juniper SRX300
Juniper SRX320
Juniper SRX340
Juniper SRX345
Juniper Srx380
Juniper Srx400
Juniper SRX4100
Juniper Srx4120
Juniper SRX4200
Juniper SRX4300
Juniper Srx440
Juniper SRX4600
Juniper SRX4700
Juniper SRX5400
Juniper SRX5600
Juniper SRX5800

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Juniper Networks Junos OS to a version that resolves this vulnerability.

    Fixed in 23.2R2-S7
  2. Upgrade

    Upgrade Juniper Networks Junos OS to a version that resolves this vulnerability.

    Fixed in 23.4R2-S6
  3. Upgrade

    Upgrade Juniper Networks Junos OS to a version that resolves this vulnerability.

    Fixed in 24.2R2-S3
  4. Upgrade

    Upgrade Juniper Networks Junos OS to a version that resolves this vulnerability.

    Fixed in 24.4R2-S4
  5. Upgrade

    Upgrade Juniper Networks Junos OS to a version that resolves this vulnerability.

    Fixed in 25.2R1-S1
  6. Compensating control

    On MX with SPC3 and SRX devices configured for VPN service, monitor tunnel up/down events; if many events occur over an extended period, it becomes likely the iked DoS condition is occurring (index value cannot be monitored).

  7. Operational

    To restore service after iked crash loops, reboot the system.

Event History

Jul 9, 2026
CVE Published
via MITRE·09:06 PM
Data Sourced
via MITRE·09:06 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-57024?

CVE-2026-57024 has a medium severity rating of 6.9.

2

What is the risk associated with CVE-2026-57024?

CVE-2026-57024 has a risk score of 33.

3

How do I fix CVE-2026-57024?

To address CVE-2026-57024, update to the latest version of Junos OS that includes the appropriate security patches.

4

What systems are affected by CVE-2026-57024?

CVE-2026-57024 affects Juniper Networks Junos OS running on MX with SPC3 and SRX Series devices.

5

What type of vulnerability is CVE-2026-57024?

CVE-2026-57024 is classified as a Use of Multiple Resources with Duplicate Identifier vulnerability in the IKE daemon.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203