Menu

Star on GitHub · 3.2k

CVE-2025-64126

10.0 · CRITICAL

An OS command injection vulnerability exists due to improper input validation.

Published Nov 26, 2025CWE-78EPSS 2.40%

Overview

CVE-2025-64126 is a critical-severity vulnerability. It was published on November 26, 2025 and has a CVSS 3.1 base score of 10.0 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 10.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

An OS command injection vulnerability exists due to improper input

validation. The application accepts a parameter directly from user input

without verifying it is a valid IP address or filtering potentially

malicious characters. This could allow an unauthenticated attacker to

inject arbitrary commands.

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-64126?

CVE-2025-64126 is a critical-severity vulnerability. It was published on November 26, 2025 and has a CVSS 3.1 base score of 10.0 (CRITICAL).

How severe is CVE-2025-64126?

This vulnerability has a CVSS 3.1 base score of 10.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

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

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-64126?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-64126 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 CRITICAL CVEs from 2025

View all