# CVE-2024-4099: Improper Encoding or Escaping of Output in GitLab

> Attackers can exploit unsanitized AI input to hide prompt injections, potentially leading to code execution or security bypasses in GitLab EE.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 26 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-8qr9-mc3w-88c6

## What is CVE-2024-4099?

CVE-2024-4099 is a low-severity code injection vulnerability in Gitlab Gitlab, published on 26 Sep 2024. 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

An issue has been discovered in GitLab EE affecting all versions starting from 16.0 prior to 17.2.8, from 17.3 prior to 17.3.4, and from 17.4 prior to 17.4.1. An AI feature was found to read unsanitized content in a way that could have allowed an attacker to hide prompt injection.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2024-4099?

It affects 1 product.


Products: Gitlab Gitlab.

## How do I fix CVE-2024-4099?

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

## Is CVE-2024-4099 being exploited?

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

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4099 and fix it if it is affected.

What it is: CVE-2024-4099 is a low-severity code injection vulnerability in Gitlab Gitlab, published on 26 Sep 2024. 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-2024-4099 in the wild and no public exploit code.

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

## Sources

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

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