Junos OS (SRX firewalls)
CVE-2025-52984: When a static route points to a reject next-hop and a gNMI query for this route is processed, RPD crashes
A NULL Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause impact to the availability of the device.
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 | 21.2R3-S9 or later |
| Junos OS 21.4 | 21.4R3-S10 or later |
| Junos OS 22.2 | 22.2R3-S6 or later |
| Junos OS 22.4 | 22.4R3-S6 or later |
| Junos OS 23.2 | 23.2R2-S3 or later |
| Junos OS 23.4 | 23.4R2-S4 or later |
| Junos OS 24.2 | 24.2R1-S2, 24.2R2 or later |
| Junos OS Evolved 0 | 22.4R3-S7-EVO or later |
| Junos OS Evolved 23.2-EVO | 23.2R2-S3-EVO or later |
| Junos OS Evolved 23.4-EVO | 23.4R2-S4-EVO or later |
| Junos OS Evolved 24.2-EVO | 24.2R2-EVO or later |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
A NULL Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause impact to the availability of the device.
When static route points to a reject next hop and a gNMI query is processed for that static route, rpd crashes and restarts.
This issue affects:
Junos OS: * all versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S10, * 22.2 versions before 22.2R3-S6, * 22.4 versions before 22.4R3-S6, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R1-S2, 24.2R2;
Junos OS Evolved:
- all versions before 22.4R3-S7-EVO,
- 23.2-EVO
versions before 23.2R2-S3-EVO, * 23.4-EVO versions before 23.4R2-S4-EVO, * 24.2-EVO versions before 24.2R2-EVO.
Am I affected?
To be exposed to this issue the system needs to be configured for GRPC:
[ system services extension-service request-response grpc ]
and a static route needs to point to a reject next-hop as shown in the following example:
[ routing-options static route 192.0.2.0/24 next-hop 198.51.100.1 resolve ]
[ routing-options static route 198.51.100.1/32 reject]
Workarounds
There are no known workarounds for this issue. To reduce the risk of exploitation use access lists or firewall filters to limit access to the device only from trusted, administrative networks or hosts, and configure authentication for grpc.
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.