# CVE-2026-110102: powerlevel10k through 1.20.0 Download of Code Without Integrity Check in gitstatus Installer

> Attackers can intercept insecure downloads to inject malicious code into the gitstatus daemon, executing arbitrary commands as the user.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/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:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-hvg4-58mj-cjjc

## What is CVE-2026-110102?

CVE-2026-110102 is a high-severity vulnerability in romkatv powerlevel10k, published on 13 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

Powerlevel10k through 1.20.0 contains an insecure download vulnerability in the gitstatus/install script that disables TLS certificate verification with curl -k and skips integrity checks when no SHA-256 utility exists. Network-positioned attackers can intercept the github.com mirror request and substitute a malicious archive, which runs as the gitstatusd daemon under the user's account on every prompt.

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

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


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

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

## Is CVE-2026-110102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110102 is a high-severity vulnerability in romkatv powerlevel10k, published on 13 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-110102 in the wild and no public exploit code.

Affected product: romkatv powerlevel10k. 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-110102/ (Markdown: https://insights.sbomify.com/CVE-2026-110102/index.md)
```

## Sources

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

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