Junos OS (SRX firewalls)
CVE-2025-60011: Optional transitive BGP attribute is modified before propagation to peers causing sessions to flap
An Improper Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an availability impact for downstream devices.
Published
Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.
Affected and fixed versions
| Product / branch | Fixed in |
|---|---|
| Junos OS 0 | 22.4R3-S8 or later |
| Junos OS 23.2 | 23.2R2-S5 or later |
| Junos OS 23.4 | 23.4R2-S6 or later |
| Junos OS 24.2 | 24.2R2-S2 or later |
| Junos OS 24.4 | 24.4R2 or later |
| Junos OS Evolved 0 | 22.4R3-S8-EVO or later |
| Junos OS Evolved 23.2 | 23.2R2-S5-EVO or later |
| Junos OS Evolved 23.4 | 23.4R2-S6-EVO or later |
| Junos OS Evolved 24.2 | 24.2R2-S2-EVO or later |
| Junos OS Evolved 24.4 | 24.4R2-EVO or later |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
An Improper Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an availability impact for downstream devices.
When an affected device receives a specific optional, transitive BGP attribute over an existing BGP session, it will be erroneously modified before propagation to peers. When the attribute is detected as malformed by the peers, these peers will most likely terminate the BGP sessions with the affected devices and thereby cause an availability impact due to the resulting routing churn.
This issue affects:
Junos OS:
- all versions before 22.4R3-S8,
- 23.2 versions before 23.2R2-S5
- 23.4 versions before 23.4R2-S6,
- 24.2 versions before 24.2R2-S2,
- 24.4 versions before 24.4R2;
Junos OS Evolved:
- all versions before 22.4R3-S8-EVO,
- 23.2 versions before 23.2R2-S5-EVO,
- 23.4 versions before 23.4R2-S6-EVO,
- 24.2 versions before 24.2R2-S2-EVO,
- 24.4 versions before 24.4R2-EVO.
Am I affected?
To be exposed to this issue BGP needs to be configured for at least two peers via:
[ protocols bgp ... neighbor ... ]
Workarounds
There are no known workarounds for this issue.
Exploitation
Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
Sources
KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.