{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-112344 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-112344 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-112344 is a high-severity vulnerability in Syncplify, Inc. Syncplify Server!, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-112344 and fix it if it is affected.\n\nWhat it is: CVE-2026-112344 is a high-severity vulnerability in Syncplify, Inc. Syncplify Server!, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-112344 in the wild and no public exploit code.\n\nAffected product: Syncplify, Inc. Syncplify Server!. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-112344/ (Markdown: https://insights.sbomify.com/CVE-2026-112344/index.md)","id":"CVE-2026-112344","markdown":"https://insights.sbomify.com/CVE-2026-112344/index.md","name":"CVE-2026-112344","record":{"aliases":["GHSA-p96g-3942-wh9r"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Syncplify Server! 6.0.0 \u003c 8.8.0 Symbolic Link Jail Escape","id":"CVE-2026-112344","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"TTLock Android App \u003c 9.8.260718 Hardcoded BLE Pairing Key Exposure","id":"CVE-2026-112345"},"packages":[],"prev":{"headline":"Syncplify Server! \u003c 8.8.0 Permission Override Bypass via Path Casing","id":"CVE-2026-112343"},"products":["Syncplify Server!"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["Syncplify, Inc."]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-112344/"}