CVE-2025-52946

Junos OS and Junos OS Evolved: With traceoptions enabled, receipt of malformed AS PATH causes RPD crash

HIGH
7.5
CVSS Score
Published: July 11, 2025 at 02:39 PM UTC
Updated: June 17, 2026 at 09:37 AM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

A Use After Free vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Juniper Networks Junos OS Evolved allows an attacker sending a BGP update with a specifically malformed AS PATH to cause rpd to crash, resulting in a Denial of Service (DoS). Continuous receipt of the malformed AS PATH attribute will cause a sustained DoS condition. On all Junos OS and Junos OS Evolved platforms, the rpd process will crash and restart when a specifically malformed AS PATH is received within a BGP update and traceoptions are enabled. This issue only affects systems with BGP traceoptions enabled and requires a BGP session to be already established. Systems without BGP traceoptions enabled are not impacted by this issue. This issue affects: Junos OS: * All versions before 21.2R3-S9,  * all versions of 21.4, * from 22.2 before 22.2R3-S6,  * from 22.4 before 22.4R3-S5,  * from 23.2 before 23.2R2-S3,  * from 23.4 before 23.4R2-S4,  * from 24.2 before 24.2R2; Junos OS Evolved: * All versions before 22.4R3-S5-EVO,  * from 23.2-EVO before 23.2R2-S3-EVO,  * from 23.4-EVO before 23.4R2-S4-EVO,  * from 24.2-EVO before 24.2R2-EVO. This is a more complete fix for previously published CVE-2024-39549 (JSA83011).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 21.2R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R2, so it looks safe — our inference, not a vendor statement
v < 22.4R3-S5-EVO23.2-EVO ≤ v < 23.2R2-S3-EVO23.4-EVO ≤ v < 23.4R2-S4-EVO24.2-EVO ≤ v < 24.2R2-EVO23.2-EVO23.4-EVO24.2-EVO
Affected range stops below 22.4R3-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R2-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card