GitAhead versions 2.5.0 through 2.7.1 implement an insecure update mechanism that installs downloaded updates without any integrity or signature verification (CWE‑494). After a single TLS error dialog, the application permanently suppresses all future TLS errors, allowing a malicious actor to perform a man‑in‑the‑middle attack. The combined effect permits an attacker to supply a forged update that, when installed, results in arbitrary code execution with the privileges of the installing user.

The vulnerable revisions are GitAhead 2.5.0 to 2.7.1. The CVE data does not specify any operating‑system restrictions; therefore every installation of these versions on supported platforms is considered vulnerable.

The CVSS score of 7.7 categorizes the flaw as high severity. The EPSS score is not available, and the vulnerability is not listed in the KEV catalog, indicating a moderate exploitation likelihood. Attackers need only to intercept the TLS handshake between the client and the official update server; after the user dismisses the initial TLS error, the client will silently trust subsequent connections. By supplying a malicious update payload, the attacker can trigger code execution without additional user interaction, making the flaw readily exploitable in environments lacking strict network controls.