# CVE-2026-82668: klaussilveira GitList Git Command Line CommandLine.php getDefaultBranch os command injection


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-v64j-pgc3-qgc9

## What is CVE-2026-82668?

CVE-2026-82668 is a medium-severity vulnerability in klaussilveira GitList, published on 31 Aug 2026. 

### Official description

A security vulnerability has been detected in klaussilveira GitList 2.0.0. Affected by this vulnerability is the function getDefaultBranch of the file src/SCM/System/Git/CommandLine.php of the component Git Command Line. Such manipulation leads to os command injection. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 3.0.0-beta addresses this issue. The name of the patch is 88cf2866083d5f7c20d9d565c45f828a7ad1516b. Upgrading the affected component is advised.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-82668 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82668 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82668 is a medium-severity vulnerability in klaussilveira GitList, published on 31 Aug 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82668 exists.

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

## Sources

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

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