Unauthenticated remote root RCE in Juniper MX Series routers — widely deployed carrier/enterprise network infrastructure; full device and network compromise possible.
CVE-2026-102182
Unauthenticated remote root RCE in Juniper Junos MX kmd via crafted IKE certificate packets.
Is CVE-2026-102182 being exploited?
Not confirmed. CVE-2026-102182 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-102182?
CVE-2026-102182 is rated Critical with a CVSS score of 9.3. 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-102182?
Yes. A fix has been recorded for CVE-2026-102182. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102182 affect?
CVE-2026-102182 affects Juniper Junos OS on MX Series, Versions before 21.2R3-S11, 21.4 before 21.4R3-S12, 22.2 before 22.2R3-S8, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102182?
Upgrade Junos to vendor fixed releases; apply Juniper JSA hotfix; block IKE from untrusted networks.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution as root via crafted IKE certificate packets; full device compromise and network pivoting.
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.