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

> Attackers can intercept update checks and install malicious updates due to missing signature verification and TLS bypass, leading to code execution.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-6xm7-h392-mjvq

## What is CVE-2026-105295?

CVE-2026-105295 is a high-severity vulnerability in GitAhead, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-105295?


## How do I fix CVE-2026-105295?

No fix has been published for CVE-2026-105295 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105295 being exploited?

There is no known exploitation of CVE-2026-105295 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105295 and fix it if it is affected.

What it is: CVE-2026-105295 is a high-severity vulnerability in GitAhead, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-105295 in the wild and no public exploit code.

Affected product: GitAhead. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105295/ (Markdown: https://insights.sbomify.com/CVE-2026-105295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105295
- OSV: https://osv.dev/vulnerability/CVE-2026-105295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105295/
Summaries are generated and may contain mistakes; the official description above is the record.