CVE-2026-101941 Juniper Networks CVE debrief

Who should care

Network administrators and security teams responsible for Juniper Networks Junos OS and Junos OS Evolved configurations should assess exposure and apply remediation. Operators managing network infrastructure, vulnerability management teams, and security personnel should prioritize verifying configurations, assessing exposure, and applying vendor guidance to prevent potential rpd crashes and denial-of-service attacks.

Why it matters

A denial-of-service vulnerability exists in Juniper Networks Junos OS and Junos OS Evolved. Defenders should verify exposure, assess configurations, and apply vendor remediation to prevent potential rpd crashes and denial-of-service attacks.

• Verify configurations for vulnerable versions and specific routing-policy resolution-map and policy event-tracing settings to prevent potential rpd crashes.
• Assess network architecture and BGP neighbor configurations to determine exposure.
• Apply remediation or patches to prevent denial-of-service attacks.
• Monitor for suspicious BGP activity and rpd crashes to detect potential attacks.

Technical summary

A NULL Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a configured BGP neighbor to cause a denial of service via a BGP route update when specific routing-policy resolution-map and policy event-tracing configuration is enabled. This technical issue requires defenders to assess configurations, verify exposure, and apply vendor remediation to prevent potential rpd crashes and denial-of-service attacks. The vulnerability affects routing services and requires immediate attention from network administrators and security teams.

Defensive priority

Defenders should prioritize verifying exposure, assessing configurations, and applying vendor remediation.

Recommended defensive actions

• Verify Junos OS and Junos OS Evolved configurations for vulnerable versions and specific routing-policy resolution-map and policy event-tracing settings.
• Assess exposure based on network architecture and BGP neighbor configurations.
• Apply Juniper Networks' recommended remediation or patches.
• Monitor for suspicious BGP activity and rpd crashes.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE Program and NVD provide official records of the vulnerability. Juniper Networks provides a vendor advisory. Evidence is limited to public CVE details and vendor guidance. Defenders should verify configurations, assess exposure, and apply remediation based on official guidance. Limited source detail is available; explicit evidence limits apply.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.