Skip to main content

Parsec EUVDEUVD-2026-45968

| CVE-2026-25039 HIGH
Path Traversal: '\\UNC\share\name\' (Windows UNC Share) (CWE-40)
2026-07-20 GitHub_M
8.8
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Join or compromise org membership
  2. Delivery
    Create workspace named as attacker UNC path
  3. Exploit
    Victim Windows client mounts workspace
  4. Execution
    Windows auto-authenticates over SMB
  5. Persist
    Capture leaked NetNTLM hash
  6. Impact
    Crack or relay for further access

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path traversal: UNC share
Exploitation Conditions

Exploitation requires the attacker to be an authenticated member of a shared Parsec organization with the ability to create or name a workspace (CVSS PR:L), and requires that the malicious workspace name be permitted to contain the backslash character so it resolves to a UNC path such as \\host\share. Impact is realized only on the Windows client platform, where workspace names are used to build filesystem mountpoints; non-Windows clients are not described as affected. NTLM hash disclosure occurs when a victim's Windows client mounts the poisoned workspace and reaches an attacker-controlled SMB host, while an invalid/unreachable UNC target instead causes denial of service (client becomes unresponsive). Limiting factors: requires org membership, a Windows victim, and outbound SMB reachability to the attacker's server, all of which reduce the population of exploitable deployments below what the network-vector CVSS alone implies.

Impact

The supplied CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N, C:H/I:H/A:H, score 8.8) marks this as high severity: network reachable, low complexity, requiring only low privileges (PR:L, i.e. authenticated org membership) and no user interaction. There is no EPSS score, no KEV listing, and no POC reference in the provided data, so this is a high-CVSS issue without evidence of active or automated exploitation - meaning real-world urgency is driven by the credential-theft impact rather than mass exploitation. One caveat: the vendor rating of I:H (integrity high) is arguable, since the directly described impacts are credential disclosure (confidentiality) and application hang (availability); integrity impact is indirect, realized only if the stolen NetNTLM hash is subsequently cracked or relayed. Because exploitation requires being an existing member of a shared organization who can create/name a workspace, the realistic threat is an insider or a compromised collaborator rather than an anonymous internet attacker.

Exploit ScenarioDerived

An attacker who is a member of a Parsec organization creates or renames a workspace to a UNC path pointing at their SMB server, e.g. \\attacker.example\share. When other members' Windows Parsec clients mount that workspace, Windows automatically authenticates to the attacker's host and leaks each victim's NetNTLM hash for offline cracking or relay; alternatively the attacker points the name at an invalid host to freeze victims' clients. No public POC is currently identified, but the technique mirrors well-known UNC/NTLM-leak attacks.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 20, 2026

NTLM credential theft and denial-of-service in Scille Parsec (parsec-cloud before 3.3.3-rc.0) arises because the Windows client mounts organization workspaces using their unsanitized names, and a workspace name containing backslashes can evaluate to a UNC path. A low-privileged organization member who names a workspace as an attacker-controlled UNC path (e.g. \\attacker\share) forces victim clients to reach out over SMB, leaking their NetNTLM hash to the attacker or hanging the application if the path is unreachable. Publicly available exploit code has not been identified and it is not in CISA KEV, though a fixed vendor release exists.

RemediationAI

Vendor-released patch: upgrade parsec-cloud to 3.3.3-rc.0 or later, which sanitizes workspace names before they are used to build Windows mountpoints; consult the vendor advisory GHSA-qx56-wxpm-j4m6 (https://github.com/Scille/parsec-cloud/security/advisories/GHSA-qx56-wxpm-j4m6) for the released version. Where immediate patching is not possible, compensating controls include administratively vetting/blocking workspace names that contain backslash characters or UNC-like prefixes (\\), and restricting who may create or rename workspaces to trusted administrators to reduce the pool of potential attackers. At the network layer, block outbound SMB (TCP 445 and legacy 137-139) from Parsec client hosts to untrusted destinations so coerced UNC connections cannot reach an attacker's server, and enforce SMB signing and disable NTLM where feasible; the trade-off is that outbound-SMB blocking may break legitimate file-share access and NTLM hardening can disrupt other Windows integrations, so test before rollout.

Affected VersionsENISA

parsec-cloud < 3.3.3-rc.0

Affected Packages

euvd parsec_cloud fix: 3.3.3-rc.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Parsec is a cryptographically secure, cloud-based file-sharing application; on Windows it exposes each organization workspace as a filesystem mountpoint. The flaw is a Windows UNC share path injection (CWE-40, 'Path Traversal: \\UNC\share\name\'): because the backslash character is permitted in workspace names and the name is used verbatim when constructing the mountpoint, a name such as \\host\share is interpreted by the Windows filesystem/SMB stack as a remote UNC target rather than a local label. When Windows resolves that UNC path it automatically initiates an SMB/NTLM authentication handshake to the specified host, which is the classic vector for coercing a machine to disclose its NetNTLMv1/v2 challenge-response (the 'NTLM hash' referenced in the advisory). The affected component is cpe:2.3:a:scille:parsec-cloud, and the trigger is entirely within the workspace-naming feature.

Know when Parsec Cloud gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Attacker needs org membership to create a workspace (PR:L) but no victim interaction (UI:N); NTLM disclosure and client hang give C:H/A:H, while integrity impact is only indirect (I:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Jul 20, 2026 - 17:02 EUVD
CVE Published
Jul 20, 2026 - 14:53 cve.org
HIGH 8.8

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Scille Parsec Windows clients (before version 3.3.3-rc.0) are vulnerable to NTLM credential theft and application denial-of-service attacks initiated by malicious organization members. Compromised credentials could enable lateral movement and unauthorized access to downstream systems, making this a material risk for any organization with Windows-based Parsec deployments.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 73% exploitable
Prevalence
Low
niche vendor secure file-sharing app, limited enterprise footprint
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy