---
id: CVE-2026-106079
title: >-
  Session Smart Router and Session Smart Conductor: Improper validation of a
  field causes privilege escalation when updating the YANG configuration
summary: "An Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability\_in AccessManager in Juniper Networks Session Smart Router and Session Smart Conductor allows an attacker with config-write privil…"
severity: high
cvss: 8.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cvssSource: cna
cwe:
  - CWE-78
vendor: Juniper Networks
product: Session Smart Router
affected:
  - session_smart_router < 7.0.5
  - session_smart_router >= 7.1.0 < 7.1.7
  - session_smart_router >= 7.2.0 < 7.2.3
  - session_smart_conductor < 7.0.5
  - session_smart_conductor >= 7.1.0 < 7.1.7
  - session_smart_conductor >= 7.2.0 < 7.2.3
published: '2026-10-28'
updated: '2026-10-28'
sourceUpdated: '2026-10-28T16:37:49.668Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-106079'
references:
  - url: 'https://supportportal.juniper.net/JSA112183'
tags:
  - cve.org
ingestedAt: '2026-10-28T17:14:44.467Z'
---

## Overview

An Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in AccessManager in Juniper Networks Session Smart Router and Session Smart Conductor allows an attacker with config-write privileges to achieve arbitrary command execution as root in the YANG configuration.

## Affected

- `session_smart_router < 7.0.5`
- `session_smart_router >= 7.1.0 < 7.1.7`
- `session_smart_router >= 7.2.0 < 7.2.3`
- `session_smart_conductor < 7.0.5`
- `session_smart_conductor >= 7.1.0 < 7.1.7`
- `session_smart_conductor >= 7.2.0 < 7.2.3`

## Remediation

The following software releases of Session Smart Router and Session Smart Conductor have been updated to resolve these specific issues:
  *  7.0.5 

and all subsequent releases;
  *  7.1.7 

and all subsequent releases;
  *  7.2.3 and all subsequent releases.

### Workarounds

There are no known workarounds for this issue.
