CVE-2025-40896: Lack of TLS certificate validation when connecting Arc to a Guardian or CMC, in Arc before v2.2.0
The server certificate was not verified when an Arc agent connected to a Guardian or CMC.
A malicious actor could perform a man-in-the-middle attack and intercept the communication between the Arc agent and the Guardian or CMC. This could result in theft of the client token and sensitive information (such as assets and alerts), impersonation of the server, or injection of spoofed data (such as false asset information or vulnerabilities) into the Guardian or CMC.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-40896?
CVE-2025-40896 has a high severity rating due to its potential for man-in-the-middle attacks.
How do I fix CVE-2025-40896?
To fix CVE-2025-40896, upgrade Arc to version 2.2.0 or later to ensure TLS certificate validation is properly implemented.
Who is affected by CVE-2025-40896?
CVE-2025-40896 affects Arc versions prior to 2.2.0 that connect to a Guardian or CMC without proper certificate verification.
What type of attack does CVE-2025-40896 enable?
CVE-2025-40896 potentially enables man-in-the-middle attacks where an attacker can intercept communications between the Arc agent and the server.
What are the implications of CVE-2025-40896?
The implications of CVE-2025-40896 include unauthorized access and data interception, compromising the confidentiality and integrity of the communication.