# CVE-2026-103407: An Improper Limitation of a Pathname to a Restricted Directory vulnerability in ConfigDirector in Juniper Networks Session Smart Router and


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-349q-fx25-2p3q

## What is CVE-2026-103407?

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

### Official description

An Improper Limitation of a Pathname to a Restricted Directory vulnerability in ConfigDirector in Juniper Networks Session Smart Router and Session Smart Conductor allows an authenticated REST user to read, overwrite, or delete arbitrary certificate and key files on the host filesystem via the certificate and private-key REST API.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-103407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103407 is a high-severity vulnerability in Juniper Networks Session Smart Conductor, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103407 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-103407/ (Markdown: https://insights.sbomify.com/CVE-2026-103407/index.md)
```

## Sources

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

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