CVE-2026-105295
Description
GitAhead 2.5.0 through 2.7.1 contains an insecure update mechanism that installs downloaded updates without integrity or signature verification and permanently ignores TLS errors after one SSL error dialog. Network attackers presenting an invalid certificate once can intercept later automatic update checks, offer a fake version, and execute code as the user upon installation.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://github.com/gitahead/gitahead
- https://github.com/gitahead/gitahead/blob/v2.7.1/src/app/Application.cpp#L284-L309
- https://github.com/gitahead/gitahead/blob/v2.7.1/src/update/Updater.cpp#L176-L279
- https://github.com/gitahead/gitahead/issues/662
- https://www.vulncheck.com/advisories/gitahead-2.5.0-through-2.7.1-unverified-update-installation-and-tls-bypass
CWEs
CWE-494
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.