Impacts Juniper SRX/MX packet-forwarding; can cause complete traffic-processing DoS on core network devices used by enterprises and service providers — high operational impact.
CVE-2026-102081
Memory leak in Juniper PFE on SRX/MX can cause complete network DoS
Is CVE-2026-102081 being exploited?
Not confirmed. CVE-2026-102081 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-102081?
CVE-2026-102081 is rated High with a CVSS score of 8.7. 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-102081?
Yes. A fix has been recorded for CVE-2026-102081. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102081 affect?
CVE-2026-102081 affects Juniper Junos OS on SRX Series (SRX4000, SRX5000 w/SPC3), Juniper Junos OS on MX Series (MX w/SPC3), Affected Junos versions: 23.4R2-S3 < 23.4R2-S7; 24.2R2 < 24.2R2-S3; 24.4 < 24.4R2-S3; 25.2 < 25.2R1-S2,25.2R2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102081?
Upgrade to vendor-fixed Junos ASAP; monitor PFE memory; limit high conn/sec and disable affected services.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated network attacker can trigger PFE memory leak via high conn/sec churn with specific services enabled, causing complete traffic-processing DoS.
Immediate action required
- affected>= 23.4R2-S3 and < 23.4R2-S7
- affected>= 24.2R2 and < 24.2R2-S3
- affected>= 24.4 and < 24.4R2-S3
- affected>= 25.2 and < 25.2R1-S2, 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.