CVE-2026-101970: Junos OS and Junos OS Evolved: Specific PIM messages causes rpd crash when multiple-triggered-joins is used

Published Oct 14, 2026
·
Updated

A Use After Free vulnerability in the rpd PIM Join/Prune processing of Juniper Networks Junos OS and Junos OS Evolved platforms allows an unauthenticated adjacent attacker to crash the routing daemon via specific PIM messages when sparse mode PIM is configured.

Affected Software

2 affected components
Juniper Networks Junos OS
Juniper Networks Junos OS Evolved

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 23.2R2-S7.7-EVO
  2. Upgrade

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

    Fixed in 23.4R2-S8.11-EVO
  3. Upgrade

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

    Fixed in 24.2R2-S5.6-EVO
  4. Upgrade

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

    Fixed in 24.4R2-S5-EVO
  5. Upgrade

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

    Fixed in 25.2R2-S2-EVO
  6. Upgrade

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

    Fixed in 25.2X100-D35-EVO
  7. Upgrade

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

    Fixed in 25.4R1-S3-EVO
  8. Upgrade

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

    Fixed in 25.4R2-EVO
  9. Upgrade

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

    Fixed in 25.4X300-D40-EVO
  10. Upgrade

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

    Fixed in 26.2R1-S2-EVO
  11. Upgrade

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

    Fixed in 26.2R2-EVO
  12. Upgrade

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

    Fixed in 26.4R1-EVO
  13. Upgrade

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

    Fixed in 23.2R2-S7.7
  14. Upgrade

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

    Fixed in 23.4R2-S8.13
  15. Upgrade

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

    Fixed in 24.2R2-S5.5
  16. Upgrade

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

    Fixed in 24.4R2-S5
  17. Upgrade

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

    Fixed in 25.2R2-S2
  18. Upgrade

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

    Fixed in 25.4R1-S3
  19. Upgrade

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

    Fixed in 25.4R2
  20. Upgrade

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

    Fixed in 26.2R1-S2
  21. Upgrade

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

    Fixed in 26.2R2
  22. Upgrade

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

    Fixed in 26.4R1

Event History

Oct 14, 2026
CVE Published
via MITRE·04:43 PM
Data Sourced
via MITRE·04:43 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An unauthenticated attacker on an adjacent network can exploit it by sending specific PIM messages. The attack does not require user interaction or prior privileges.

2

Which deployments are exposed?

Exposure requires sparse-mode PIM to be configured and use of multiple-triggered-joins. The affected software includes Juniper Networks Junos OS and Junos OS Evolved.

3

What is the operational impact?

Successful exploitation can crash the routing daemon (rpd), causing an availability impact. No confidentiality or integrity impact is identified in the supplied severity vector.

4

How can I assess whether a device is at risk?

Review the device configuration to determine whether sparse-mode PIM is enabled and whether multiple-triggered-joins is in use. Devices without those stated conditions are not identified as exposed by the provided information.

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