# CVE-2026-112344: Syncplify Server! 6.0.0 < 8.8.0 Symbolic Link Jail Escape


- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-p96g-3942-wh9r

## What is CVE-2026-112344?

CVE-2026-112344 is a high-severity vulnerability in Syncplify, Inc. Syncplify Server!, published on 26 Oct 2026. 

### Official description

Syncplify Server! 6.0.0 before 8.8.0 contains a path traversal vulnerability that allows attackers with a symbolic link placed inside a user's home folder to access files outside the virtual filesystem root because confinement is enforced only against the requested path and not the on-disk destination of the link. Attackers can leverage a symlink or, on Windows, a directory junction that points outside the jail to read or access restricted files beyond the intended home-folder boundary.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-112344 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112344 is a high-severity vulnerability in Syncplify, Inc. Syncplify Server!, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112344 in the wild and no public exploit code.

Affected product: Syncplify, Inc. Syncplify Server!. 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-112344/ (Markdown: https://insights.sbomify.com/CVE-2026-112344/index.md)
```

## Sources

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

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