Widely deployed Junos OS line-card infrastructure; root access on multiple devices could disrupt networks across many industries.
CVE-2025-30650
Missing auth in Junos OS command processing lets local attacker gain root on line cards.
Is CVE-2025-30650 being exploited?
Not confirmed. CVE-2025-30650 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2025-30650?
CVE-2025-30650 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-30650?
Yes. A fix has been recorded for CVE-2025-30650. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-30650 affect?
CVE-2025-30650 affects Juniper Networks Junos OS line cards: MPC7-11, LC2101/LC2103, LC480/LC4800/LC9600, MX304 (built-in FPC), MX-SPC3, SRX5K-SPC3, EX9200-40XS, FPC3-PTX-U2/U3, FPC3-SFF-PTX, LC1101/LC1102/LC1104/LC1105, Junos OS versions affected: before 22.4R3-S8; before 23.2R2-S6; before 23.4R2-S6; before 24.2R2-S3; before 24.4R2; before 25.2R2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-30650?
Upgrade to fixed Junos OS release per advisories
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can escalate to root on affected Junos line cards via privileged command processing, potentially taking full device control.
Immediate action required
- affected< 22.4R3-S8
- affected>= 23.2 and < 23.2R2-S6
- affected>= 23.4 and < 23.4R2-S6
- affected>= 24.2 and < 24.2R2-S3
- affected>= 24.4 and < 24.4R2
- affected>= 25.2 and < 25.2R2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.