Menu

Star on GitHub · 3.2k

CVE-2025-36613

2.8 · LOW

SupportAssist for Home PCs versions 4.6.3 and prior and SupportAssist for Business PCs versions 4.5.3 and prior, contain(s) an Incorrect Privilege Assignment vulnerability.

Published Aug 14, 2025CWE-266EPSS 0.11%

Overview

CVE-2025-36613 is a low-severity vulnerability. It was published on August 14, 2025 and has a CVSS 3.1 base score of 2.8 (LOW).

This vulnerability has a CVSS 3.1 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

SupportAssist for Home PCs versions 4.6.3 and prior and SupportAssist for Business PCs versions 4.5.3 and prior, contain(s) an Incorrect Privilege Assignment vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to unauthorized access.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-36613?

CVE-2025-36613 is a low-severity vulnerability. It was published on August 14, 2025 and has a CVSS 3.1 base score of 2.8 (LOW).

How severe is CVE-2025-36613?

This vulnerability has a CVSS 3.1 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-36613?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-36613?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-36613 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2025

View all