dbcve.org
JunosOperating system · Juniper

CVE-2026-57024

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 23.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Use of Multiple Resources with Duplicate Identifier vulnerability in the IKE daemon (iked) of Juniper Junos OS on MX with SPC3 and SRX Series allows an unauthenticated attacker to cause a DoS. When many VPN negotiations fail, a peer index rollover assigns duplicate index values to new peers, causing the iked process to crash repeatedly and preventing new VPN connections and rekeying of existing tunnels.

MitigationApply vendor-provided patches by upgrading to the fixed versions (23.2R2-S7, 23.4R2-S6, 24.2R2-S3, 24.4R2-S4, or 25.2R1-S1 and later). Monitor tunnel events closely; if abnormal negotiation failures occur over extended periods, a system reboot may be required to restore service until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 23.2= 23.2= 23.4= 24.2= 24.4= 25.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device platform
    Run 'show chassis hardware' or 'show system information' to confirm the device is an MX Series with SPC3 or an SRX Series device
    Affected if Device is NOT an MX with SPC3 or SRX Series (vulnerability only affects these platforms)
  2. Check Junos OS version
    Run 'show version' and compare the installed Junos version against the affected ranges: versions < 23.2, 23.2, 23.4, 24.2, 24.4, or 25.2
    Affected if Installed version matches any of the affected versions listed
  3. Verify IKE daemon is active
    Run 'show system processes iked' or check if iked process is running with 'ps aux | grep iked'
    Affected if iked process is running (vulnerability requires IKE/IPSec VPN functionality to be enabled)
  4. Inspect for iked crash events
    Run 'show log messages' or 'show log iked' and search for iked process crash entries, particularly those mentioning 'peer index' or 'duplicate'
    Affected if Multiple iked crash events are logged, especially with peer index rollover errors
  5. Check for VPN negotiation failures
    Run 'show ike sa' and 'show ipsec sa' to inspect tunnel status; review logs for negotiation failures preceding crashes
    Affected if High volume of failed VPN negotiations observed, followed by iked process restarts

Device is affected if it is an MX with SPC3 or SRX Series, runs an affected Junos version, has IKE/IPSec configured, and exhibits iked crashes with peer index errors following VPN negotiation failures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.2 or later
Fixed in 23.2
Interim mitigation

Apply vendor-provided patches by upgrading to the fixed versions (23.2R2-S7, 23.4R2-S6, 24.2R2-S3, 24.4R2-S4, or 25.2R1-S1 and later). Monitor tunnel events closely; if abnormal negotiation failures occur over extended periods, a system reboot may be required to restore service until the patch is applied.

Recommended fix High confidence

23.2R2-S7, 23.4R2-S6, 24.2R2-S3, 24.4R2-S4, or 25.2R1-S1 (depending on current version branch)

  1. 1. Identify the current Junos OS version on the affected MX with SPC3 or SRX device using 'show version'
  2. 2. Verify the iked process is running (vs kmd) using 'show system processes extensive | match "KMD|IKED"'
  3. 3. Determine the appropriate upgrade path based on current version: for 23.2.x upgrade to 23.2R2-S7 or later; for 23.4.x upgrade to 23.4R2-S6 or later; for 24.2.x upgrade to 24.2R2-S3 or later; for 24.4.x upgrade to 24.4R2-S4 or later; for 25.2.x upgrade to 25.2R1-S1 or later
  4. 4. Schedule a maintenance window as upgrade will require system reboot
  5. 5. Download the appropriate Junos upgrade image from Juniper support portal
  6. 6. Upload the upgrade image to the device and initiate upgrade using 'request system software add <package> reboot'
  7. 7. After reboot, verify the new version is running with 'show version'
  8. 8. Verify iked process is stable with 'show system processes extensive | match IKED' and monitor for any crashes
Caveat Standard Junos upgrade may cause temporary service interruption; ensure valid configuration backup before upgrade; some legacy VPN configurations may require review post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57024 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data