OS command injection enables root command execution in Juniper Networks Session Smart Router and Session Smart Conductor

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-106079?

CVE-2026-106079 is a vulnerability classified as Improper Neutralization of Special Elements used in an OS Command, affecting Session Smart Router (affected versions: < 7.0.5, 7.1.0 – < 7.1.7, and other affected versions) and Session Smart Conductor (affected versions: < 7.0.5, 7.1.0 – < 7.1.7, and other affected versions). This vulnerability is rated High, with a CVSS score of 8.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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 products and scope

  • Session Smart Router: Affected while the default status is marked unaffected outside the listed ranges, with affected versions from 0 to less than 7.0.5, from 7.1.0 to less than 7.1.7, or from 7.2.0 to less than 7.2.3.
  • Session Smart Conductor: Affected in the same ranges: from 0 to less than 7.0.5, from 7.1.0 to less than 7.1.7, or from 7.2.0 to less than 7.2.3.
  • Juniper states that 7.0.5, 7.1.7, and 7.2.3, together with subsequent releases in the corresponding branches, were updated to resolve the issue. A fix in one parallel branch should not be treated as proof that another branch is unaffected.

Technical details

The flaw is classified as CWE-78 and resides in AccessManager while processing a field during YANG configuration updates. Improper neutralization of special elements allows attacker-controlled data to reach an operating-system command context, resulting in arbitrary command execution as root. The confirmed precondition is that the attacker has config-write privileges and can reach the configuration function over the network; no additional user interaction is required. The record does not identify the specific field, endpoint, command-construction function, or payload syntax, so those implementation details remain publicly unknown.

Exploitability

  • Reachability: The vulnerable function is reachable over the network.
  • Privilege requirement: The attacker must already have config-write privileges on the target system.
  • Interaction and complexity: The record describes no user interaction and low attack complexity.
  • Exploitation status: Juniper SIRT stated that it was not aware of malicious exploitation of the vulnerabilities covered by the bulletin at the time of publication. The record does not identify a public exploit and does not establish that exploitation is impossible.

Technical impact

The flaw lets a user with config-write privileges move from authorized configuration activity to operating-system command execution as root on the device. Potential technical consequences include loss of confidentiality, unauthorized modification of system or network state, and disruption of device availability. Based on the available evidence, the immediate scope is the exploited device; automatic propagation to other systems is not described. The requirement for config-write privileges limits who can reach the vulnerable operation, but it does not remove the need to upgrade.

Business impact

Successful exploitation could give an attacker root-level control of the affected device. Depending on the data and services present, that access could expose sensitive information, alter network or management configuration, or disrupt device operations. The practical risk depends on how widely config-write privileges are assigned and whether the configuration interface is reachable from an attacker-controlled network position. The record does not establish that a breach, data loss, or service outage has occurred.

Remediation

  1. Upgrade first: Update Session Smart Router and Session Smart Conductor to the fixed release appropriate for the deployed branch: 7.0.5 and subsequent releases; 7.1.7 and subsequent releases; or 7.2.3 and subsequent releases.
  2. Match the upgrade to the correct affected branch for each product. Installing a fix on one branch does not by itself establish coverage for parallel branches.
  3. Juniper reports no known workaround for this issue. While an upgrade is pending, review and minimize config-write access to accounts that genuinely require it, and restrict network access to the configuration interface. This is temporary risk reduction, not a substitute for patching.
  4. After upgrading, verify the installed release on both products and review YANG configuration changes generated during the maintenance window.

Detection

  • Inventory systems running Session Smart Router or Session Smart Conductor, then compare their installed releases with the affected branches and fixed releases listed in the remediation section.
  • Identify accounts and roles with config-write privileges, especially on devices whose configuration interfaces are reachable over the network.
  • Review audit logs and administrative history for unexpected YANG configuration updates, unplanned privilege changes, or anomalous administrative activity. This is precautionary monitoring, not a vendor-confirmed indicator.
  • No specific field name, log event, IOC, or command pattern is provided in the available evidence. The absence of such evidence does not demonstrate that a system is safe.
Sources (15)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.