# CVE-2026-108913: Code injection in Omarchy

> Attackers can execute arbitrary code by placing malicious executable content in theme files from untrusted Git repositories.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L`)
- **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:** 11 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-mr95-xr25-7hp2, GHSA-mxm5-5433-ggf5

## What is CVE-2026-108913?

CVE-2026-108913 is a high-severity code injection vulnerability in Omarchy, published on 11 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

omarchy-theme-set in Omarchy 4 before 4.0.1 allows code execution via a third-party theme because the files placed into ~/.local/state/omarchy/current/theme may include executable content from an untrusted Git repository.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-108913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108913 is a high-severity code injection vulnerability in Omarchy, published on 11 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-108913 in the wild and no public exploit code.

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

## Sources

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

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