What is the CVSS score of CVE-2025-26817?

CVE-2025-26817 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 2.7%.

Which versions of Password Secure are affected by CVE-2025-26817?

Organizations using Netwrix Password Secure 9.2.0.32454 face critical risk from CVE-2025-26817, a OS command injection vulnerability rated CVSS 9.8.

How to fix or mitigate CVE-2025-26817?

Within 24 hours: Identify all affected systems and apply vendor patches immediately. Validate that input sanitization is in place for all user-controlled parameters.

Password Secure CVE-2025-26817

CRITICAL

OS Command Injection (CWE-78)

2025-04-03 cve@mitre.org

Command Injection Password Secure

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:34 vuln.today

CVE Published

Apr 03, 2025 - 20:15 nvd

CRITICAL 9.8

DescriptionCVE.org

Netwrix Password Secure 9.2.0.32454 allows OS command injection.

AnalysisAI

Netwrix Password Secure 9.2.0.32454 allows OS command injection. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. Netwrix Password Secure 9.2.0.32454 allows OS command injection. Affected products include: Netwrix Password Secure.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.