# CVE-2026-97229: A booby-trapped setup file can take over a GitLab server

Status: Being used now (CISA KEV, added 2026-10-29)
Who: Anyone who runs their own GitLab server, Community or Enterprise Edition.
Do this: Apply GitLab's latest security update to your self-run GitLab server.

## Agent prompt (read-only)
Read-only check, change nothing, send nothing anywhere.
Is GitLab Community Edition and Enterprise Edition (CVE-2026-97229) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2026-97229. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.

## Official description
GitLab Community Edition and Enterprise Edition contain a integer overflow or wraparound vulnerability that could allow an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation.

## Sources
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/
- https://nvd.nist.gov/vuln/detail/CVE-2026-97229
- https://nvd.nist.gov/vuln/detail/CVE-2026-97229

Generated by isitexploited.org from public sources. Verify version numbers against the vendor before acting.