High severity · published Oct 28, 2026
CVE-2026-103407
Session Smart Router and Session Smart Conductor: Unsanitized input allows arbitrary file read, overwrite, or deletion via the PKI management
New
8.8
CVSS
–
EPSS
No
On KEV
Description
An Improper Limitation of a Pathname to a Restricted Directory vulnerability in ConfigDirector in Juniper Networks Session Smart Router and Session Smart Conductor allows an authenticated REST user to read, overwrite, or delete arbitrary certificate and key files on the host filesystem via the certificate and private-key REST API.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SS
Session Smart Conductor · Juniper Networks
before 7.0.5; 7.1.0 before 7.1.7; 7.2.0 before 7.2.3 · source: vendor
SS
Session Smart Router · Juniper Networks
before 7.0.5; 7.1.0 before 7.1.7; 7.2.0 before 7.2.3 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-103407
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-103407
vendor-advisory
https://supportportal.juniper.net/JSA112183
More from Session Smart Conductor
9.8
CVE-2026-103406
Session Smart Conductor: An unauthenticated attacker causes arbitrary command execution during key management.
9.8
CVE-2025-21589
Session Smart Router, Session Smart Conductor, WAN Assurance Router: API Authentication Bypass vulnerability
8.8
CVE-2026-106079
Session Smart Router and Session Smart Conductor: Improper validation of a field causes privilege escalation when updating the YANG configuration
8.8
CVE-2026-103403
Session Smart Router and Session Smart Conductor: Unvalidated input causes arbitrary file deletion and command execution when deleting audit rules
8.8
CVE-2026-103402
Session Smart Router and Session Smart Conductor: Lack of integrity verification in cache files causes arbitrary code execution and privilege escalation