# CVE-2026-103400: An Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the ember service in


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hf87-h3v7-pm52

## What is CVE-2026-103400?

CVE-2026-103400 is a medium-severity vulnerability in Juniper Networks Session Smart Conductor, published on 28 Oct 2026. 

### Official description

An Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the ember service in Juniper Networks Session Smart Router and Session Smart Conductor allows an attacker with local access to unmount arbitrary filesystems or cause a denial of service via the creation of specially named directories and a service restart.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-103400?


## How do I fix CVE-2026-103400?

No fix has been published for CVE-2026-103400 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103400 being exploited?

There is no known exploitation of CVE-2026-103400 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103400 and fix it if it is affected.

What it is: CVE-2026-103400 is a medium-severity vulnerability in Juniper Networks Session Smart Conductor, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103400 in the wild and no public exploit code.

Affected product: Juniper Networks Session Smart Conductor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103400/ (Markdown: https://insights.sbomify.com/CVE-2026-103400/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103400
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103400
- OSV: https://osv.dev/vulnerability/CVE-2026-103400

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103400/
Summaries are generated and may contain mistakes; the official description above is the record.