{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25039 exists.","fix":"No fix has been published for CVE-2026-25039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25039 is a high-severity vulnerability in Scille parsec-cloud, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25039 and fix it if it is affected.\n\nWhat it is: CVE-2026-25039 is a high-severity vulnerability in Scille parsec-cloud, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25039 exists.\n\nAffected product: Scille parsec-cloud. 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-25039/ (Markdown: https://insights.sbomify.com/CVE-2026-25039/index.md)","id":"CVE-2026-25039","markdown":"https://insights.sbomify.com/CVE-2026-25039/index.md","name":"CVE-2026-25039","record":{"aliases":["GHSA-qx56-wxpm-j4m6"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Parsec file sharing","requires_auth":"low_privilege","summary":"Attackers can trigger NTLM hash disclosure or application hangs by using UNC paths in workspace names, affecting Parsec desktop users.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-40","name":"Path Traversal: '\\\\UNC\\share\\name\\' (Windows UNC Share)"}],"description":"Parsec is a cloud-based application for simple and cryptographically secure file sharing. The application does not sanitize the workspace name, creating a vulnerability if that workspace name is a UNC path. When creating mountpoint in the windows filesystem to mount the workspace of an organization, the application does not sanitize the workspace name. The cause issue if the workspace name evaluate to a UNC path since it's allowed for the name to containt `\\` char. If the UNC path is invalid (or the targeted resource is not available) the application become unresponsive otherwise the system will interact with the mounted UNC path allowing the attacker to retrieve to [`NTLM`] hash.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"The application evaluate UNC path in workspace name","id":"CVE-2026-25039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Budibase Vulnerable to Privilege Escalation via API Abuse – Creator Can Invite Users with Admin/Any Role","id":"CVE-2026-25040"},"packages":[],"prev":{"headline":"Gitea private organization labels are visible to unauthorized users","id":"CVE-2026-25038"},"products":["parsec-cloud"],"published":"2026-07-20","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["Scille"]},"summary":"Attackers can trigger NTLM hash disclosure or application hangs by using UNC paths in workspace names, affecting Parsec desktop users.","url":"https://insights.sbomify.com/CVE-2026-25039/"}