CVE-2026-105295 json
GitAhead 2.5.0 through 2.7.1 Unverified Update Installation and TLS Bypass
published 2026-10-05 35 d ago modified 2026-10-06 34 d ago also EUVD-2026-92159
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 35 d ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.7 | 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 |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 7.7 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- gitahead GitAhead
Classification
- Weakness
-
- CWE-494 Download of Code Without Integrity Check
References
-
github.com
/gitahead/gitahead/issues/662
issue-tracking
-
github.com
/gitahead/gitahead
product
-
github.com
/gitahead/gitahead/blob/v2.7.1/src/update/Updater.cpp#L176-L279
technical-description
-
github.com
/gitahead/gitahead/blob/v2.7.1/src/app/Application.cpp#L284-L309
technical-description
-
vulncheck.com
/advisories/gitahead-2.5.0-through-2.7.1-unverified-update-installation-and-tls-bypass
third-party-advisory
Sources
- CVE List CVE-2026-105295
- NVD CVE-2026-105295
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.