# CVE-2026-82669: klaussilveira GitList XML Parsing CommandLine.php SimpleXMLElement denial of service


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

## What is CVE-2026-82669?

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

### Official description

A vulnerability was detected in klaussilveira GitList 2.0.0. Affected by this issue is the function SimpleXMLElement of the file src/SCM/System/Git/CommandLine.php of the component XML Parsing. Performing a manipulation results in denial of service. The attack is possible to be carried out remotely. The exploit is now public and may be used. Upgrading to version 3.0.0-beta can resolve this issue. The patch is named f67609d52c1812fa8a7ed80eae5e795cfd72115f. It is advisable to upgrade the affected component.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-82669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82669 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-82669 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-82669/ (Markdown: https://insights.sbomify.com/CVE-2026-82669/index.md)
```

## Sources

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

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