Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13919: CWE-427 Uncontrolled Search Path Element in Broadcom Symantec Endpoint Protection Windows Client

0
Medium
VulnerabilityCVE-2025-13919cvecve-2025-13919cwe-427
Published: Wed Jan 28 2026 (01/28/2026, 16:41:02 UTC)
Source: CVE Database V5
Vendor/Project: Broadcom
Product: Symantec Endpoint Protection Windows Client

Description

CVE-2025-13919 is a medium severity vulnerability affecting Broadcom's Symantec Endpoint Protection Windows Client prior to versions 14. 3 RU10 Patch 1, RU9 Patch 2, and RU8 Patch 3. It involves an uncontrolled search path element (CWE-427) that allows an attacker with limited privileges to hijack COM references in the Windows Registry. This hijacking can enable persistence and evasion of detection by redirecting legitimate COM object calls to malicious payloads. The vulnerability requires local access with low privileges and does not require user interaction. Although no known exploits are currently in the wild, the vulnerability impacts the integrity and availability of affected systems. European organizations relying on Symantec Endpoint Protection for endpoint security should prioritize patching to mitigate risks. Countries with significant deployments of Broadcom security products and critical infrastructure are more likely to be targeted. Mitigation involves applying vendor patches, auditing COM registry entries, and enforcing strict access controls on registry keys related to COM objects.

AI-Powered Analysis

AILast updated: 02/05/2026, 08:34:09 UTC

Technical Analysis

CVE-2025-13919 is a vulnerability classified under CWE-427 (Uncontrolled Search Path Element) affecting Broadcom's Symantec Endpoint Protection Windows Client versions prior to 14.3 RU10 Patch 1, RU9 Patch 2, and RU8 Patch 3. The issue arises from the way the software handles COM (Component Object Model) references in the Windows Registry. An attacker with low-level privileges on a compromised or insider system can manipulate the search path for COM objects by hijacking registry entries. This hijacking allows the attacker to redirect legitimate COM object calls to malicious components, thereby establishing persistence on the system and evading detection mechanisms typically employed by endpoint protection software. The vulnerability does not require user interaction but does require local access with limited privileges, making it a post-compromise persistence technique rather than an initial infection vector. The CVSS 3.1 base score is 4.4 (medium), reflecting limited impact on confidentiality but notable impacts on integrity and availability due to potential tampering with security software components. No public exploits have been reported yet, but the vulnerability's nature makes it a concern for environments relying heavily on Symantec Endpoint Protection for security enforcement. The lack of patch links in the provided data suggests organizations should verify with Broadcom for the latest updates and advisories. The vulnerability highlights the risks of insecure search paths in security-critical software, emphasizing the need for secure handling of COM references and registry permissions.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the integrity and availability of endpoint protection systems. Successful exploitation could allow attackers to maintain persistence on critical endpoints by hijacking COM references, potentially disabling or circumventing security controls. This could lead to prolonged undetected presence of malware or unauthorized access, increasing the risk of data breaches, ransomware attacks, or sabotage. Organizations in sectors with high security requirements such as finance, healthcare, energy, and government are particularly at risk. The medium CVSS score indicates that while confidentiality is not directly impacted, the ability to undermine endpoint protection integrity can have cascading effects on overall network security. Additionally, since the vulnerability requires local access, it may be exploited in scenarios involving insider threats or after initial compromise through other vectors. The lack of known exploits currently reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits for such vulnerabilities post-disclosure. European entities using Broadcom Symantec Endpoint Protection should assess their exposure and prioritize remediation to prevent exploitation that could disrupt critical operations or lead to data loss.

Mitigation Recommendations

1. Apply the latest patches from Broadcom for Symantec Endpoint Protection Windows Client, specifically versions 14.3 RU10 Patch 1, RU9 Patch 2, or RU8 Patch 3 or later. 2. Conduct a thorough audit of COM-related registry keys to detect unauthorized modifications or suspicious entries that could indicate hijacking attempts. 3. Implement strict access control policies on registry keys associated with COM objects to limit modification rights to trusted administrators only. 4. Employ endpoint detection and response (EDR) solutions capable of monitoring registry changes and COM object loading behavior to detect potential hijacking activities. 5. Enforce the principle of least privilege for users and processes to reduce the likelihood of local privilege exploitation. 6. Educate IT and security teams about the risks of COM hijacking and the importance of monitoring persistence mechanisms. 7. Regularly review and update security policies to include checks for vulnerabilities related to search path manipulation and COM object security. 8. In environments where patching may be delayed, consider temporary compensating controls such as application whitelisting and enhanced monitoring of endpoint security software behavior.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
symantec
Date Reserved
2025-12-02T18:57:26.118Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697a41f64623b1157cda80d5

Added to database: 1/28/2026, 5:05:58 PM

Last enriched: 2/5/2026, 8:34:09 AM

Last updated: 2/7/2026, 12:26:45 AM

Views: 25

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats