Affects Juniper Junos (widely deployed network infrastructure); unauthenticated remote DoS against rmopd can disrupt network operations across organizations.
CVE-2026-102070
Unauthenticated remote DoS against Juniper Junos rmopd via TWAMP packet
Is CVE-2026-102070 being exploited?
Not confirmed. CVE-2026-102070 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-102070?
CVE-2026-102070 is rated Critical with a CVSS score of 9.2. 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-2026-102070?
Yes. A fix has been recorded for CVE-2026-102070. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102070 affect?
CVE-2026-102070 affects Juniper Junos OS (TWAMP client), Routers/switches running rmopd service. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102070?
Apply Juniper advisory JSA112188 and update Junos to patched versions immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can send a crafted TCP packet to crash or disrupt rmopd, causing network management/service outages and potential traffic control loss.
Immediate action required
- affected< 23.2R2-S7.7
- affected>= 23.4 and < 23.4R2-S8.13
- affected>= 24.2 and < 24.2R2-S5.5
- affected>= 24.4 and < 24.4R2-S5
- affected>= 25.2 and < 25.2R2-S2
- affected>= 25.4 and < 25.4R1-S3
- affected>= 26.2 and < 26.2R1-S2
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.