Affects Juniper Session Smart networking infrastructure; allows code execution and privilege escalation that can disrupt enterprise networks.
CVE-2026-103402
Arbitrary code exec & privilege escalation via unverified model cache in Juniper Session Smart.
Is CVE-2026-103402 being exploited?
Not confirmed. CVE-2026-103402 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.
How severe is CVE-2026-103402?
CVE-2026-103402 is rated High with a CVSS score of 8.8. 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-103402?
Not known from our data. No patch reference has been recorded for CVE-2026-103402, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-103402 affect?
CVE-2026-103402 affects Juniper Session Smart Router, Juniper Session Smart Conductor, PCLI/model cache. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-103402?
Restrict write access to model cache, isolate management interfaces, and apply vendor fix when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker with write access to the model cache directory can execute arbitrary code and escalate privileges on Session Smart Router/Conductor.
Immediate action required
- affected< 7.0.5
- affected>= 7.1.0 and < 7.1.7
- affected>= 7.2.0 and < 7.2.3
- affected< 7.0.5
- affected>= 7.1.0 and < 7.1.7
- affected>= 7.2.0 and < 7.2.3
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.