---
id: CVE-2026-103390
title: >-
  Session Smart Router and Session Smart Conductor: A malformed HTTP URI causes
  a service crash during HTTP application identification
summary: >-
  An Out-of-Bounds Read vulnerability in the HttpParser component in Juniper
  Networks Session Smart Router and Session Smart Conductor allows an attacker
  to cause a denial of service via a specially crafted HTTP request.
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'
cvssSource: cna
cwe:
  - CWE-125
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
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-10-29T01:37:59.693207Z'
published: '2026-10-28'
updated: '2026-10-29'
sourceUpdated: '2026-10-29T01:52:04.374Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-103390'
references:
  - url: 'https://supportportal.juniper.net/JSA112183'
tags:
  - cve.org
epss: 0.00432
epssPercentile: 0.37559
ingestedAt: '2026-10-28T17:14:44.489Z'
---

## Overview

An Out-of-Bounds Read vulnerability in the HttpParser component in Juniper Networks Session Smart Router and Session Smart Conductor allows an attacker to cause a denial of service via a specially crafted HTTP request.

## 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.