Affects Juniper Session Smart networking infrastructure; allows theft/modification of host TLS keys and certs, risking network trust, MITM, and device takeover across enterprises and ISPs.
CVE-2026-103407
Authenticated REST path traversal exposes/modifies host certs and keys on Juniper Session Smart devices.
Is CVE-2026-103407 being exploited?
Not confirmed. CVE-2026-103407 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-103407?
CVE-2026-103407 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-103407?
Yes. A fix has been recorded for CVE-2026-103407. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-103407 affect?
CVE-2026-103407 affects Juniper Session Smart Router (ConfigDirector component), Juniper Session Smart Conductor (ConfigDirector component), ConfigDirector REST certificate/private-key API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-103407?
Apply Juniper update, rotate/revoke affected certs/keys, restrict ConfigDirector access and audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can read, overwrite, or delete host TLS certificates and private keys, enabling credential theft, MITM, auth bypass, and device compromise.
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.