CVE-2026-101991 Juniper Networks CVE debrief

Who should care

Defenders responsible for Junos OS and Junos OS Evolved deployments, particularly those using BGP-LS peers and traffic-engineering routing, should assess potential exposure and impact. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, assess impact, and apply mitigations.

Why it matters

The vulnerability allows a configured BGP-LS peer to cause heap data disclosure, potentially leading to data exposure. Defenders should prioritize verifying exposure, assessing potential impact, and applying mitigations.

• Verify exposure and potential impact on Junos OS and Junos OS Evolved deployments
• Assess and mitigate potential data disclosure risks
• Review and apply vendor-provided patches or updates

Technical summary

The vulnerability is caused by improper handling of length parameter inconsistency in the routing protocol daemon (rpd) of Junos OS and Junos OS Evolved. This allows a configured BGP-LS peer to cause heap data disclosure via a malformed UPDATE sent over a session with the traffic-engineering address family enabled. The vulnerability can lead to potential data exposure and defenders should prioritize verifying exposure, assessing potential impact, and applying mitigations. Affected product context and defensive impact should be considered when assessing the vulnerability.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on BGP-LS peer configurations and traffic-engineering routing.

Recommended defensive actions

• Verify BGP-LS peer configurations and traffic-engineering routing settings
• Assess potential impact on Junos OS and Junos OS Evolved deployments
• Review and apply vendor-provided patches or updates
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and vendor advisory links. However, the details on affected versions and specific patches are limited. Defenders should verify the exposure of their Junos OS and Junos OS Evolved deployments, particularly those using BGP-LS peers and traffic-engineering routing. The vendor advisory provides additional information and mitigation guidance.

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.