# Project check: GitLab 19.5.6, 19.4.8, 19.3.9: Patch High-Severity Wiki XSS Flaw

The prompt behind the "Check your project" buttons on https://thestacksentinel.com/articles/gitlab-19-5-6-19-4-8-19-3-9-patch-high-severity-wiki-xss-flaw-e0c144d2/. Paste it into a coding agent that can read your project. It asks for a read-only check and changes nothing.

---

Check this project against a security advisory. This is a read-only check.

Advisory: GitLab 19.5.6, 19.4.8, 19.3.9: Patch High-Severity Wiki XSS Flaw
Article: https://thestacksentinel.com/articles/gitlab-19-5-6-19-4-8-19-3-9-patch-high-severity-wiki-xss-flaw-e0c144d2/
Data: CVE records on cve.org as of 2026-11-17.

Rules
- Only read files and run commands that print versions or list what is installed, for example `node --version`, `npm ls <package>`, `pip show <package>`, `docker image ls`.
- Do not install, upgrade, restart, edit, commit or delete anything, and do not send project files or data to any service.
- If a check would need a change or another command, skip it and say why.

Products and fixed releases (from the CVE records)
- GitLab: fixed in 19.3.9, 19.4.8, 19.5.6. CVEs: CVE-2026-105739 (High 8.7), CVE-2026-108153 (High 8.7), CVE-2026-18241 (High 8.2), CVE-2026-97187 (High 7.6) and 33 more
"Fixed in" lists the earliest release on each line that fixes all of that product's CVEs here. A version is not affected if it is at or above the fixed release of its own line, or on a newer line than any listed. A version on an older line with no fixed release listed is affected unless the article says otherwise. Exact ranges are in each CVE record: https://www.cve.org/CVERecord?id=<CVE id>.
The article's upgrade advice: "Checking Self-Managed GitLab Installs Against the Affected Ranges", https://thestacksentinel.com/articles/gitlab-19-5-6-19-4-8-19-3-9-patch-high-severity-wiki-xss-flaw-e0c144d2/#checking-self-managed-gitlab-installs-against-the

Steps
1. Find every place this project uses or pins these products: manifests and lockfiles (with transitive dependencies), Dockerfiles and compose files, CI configuration, infrastructure code, and version files such as .nvmrc or .tool-versions.
2. Where you can, read the version that actually runs, such as the server or runtime that handles requests, not only the command-line tool.
3. Compare each version with the affected ranges above. If the advisory's title names a product the list leaves out, take its fixed releases from the article.
4. Packages from a Linux distribution (Debian, Ubuntu, RHEL, Alpine) can carry the fix under an older version number: mark them CHECK_DISTRO and name the distribution's security tracker instead of a verdict.

Report
- A table: component | where (file:line or command) | version | verdict (AFFECTED, NOT_AFFECTED, CHECK_DISTRO or UNKNOWN).
- For each AFFECTED row, the smallest change that fixes it, as text: the file and line, and the version to move to. Do not apply it.
- What you could not check, and why.
- Finish by asking me which of these fixes, if any, I want you to apply.
