Affects widely deployed Juniper Session Smart devices; root RCE can fully compromise network infrastructure and disrupt operations.
CVE-2026-106079
Root RCE in Juniper Session Smart via AccessManager YANG config injection.
Is CVE-2026-106079 being exploited?
Not confirmed. CVE-2026-106079 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-106079?
CVE-2026-106079 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-106079?
Not known from our data. No patch reference has been recorded for CVE-2026-106079, 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-106079 affect?
CVE-2026-106079 affects Juniper Session Smart Router, Juniper Session Smart Conductor, AccessManager (YANG configuration). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-106079?
Restrict/audit config-write accounts, block management access, monitor logs, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with config-write privileges can execute arbitrary OS commands as root, enabling full device compromise and network takeover.
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.