# CVE-2018-18646: Server-side request forgery in n/a

> Server-Side Request Forgery in GitLab allows attackers to make arbitrary requests from the server, potentially accessing internal resources.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7g3x-cmv9-pp76, MINI-77fj-f7h5-jxmj, MINI-pvv3-r72m-vv69, UBUNTU-CVE-2018-18646

## What is CVE-2018-18646?

CVE-2018-18646 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 4 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in GitLab Community and Enterprise Edition before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. It allows SSRF.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2018-18646?

It affects 1 product.


Products: Gitlab Gitlab.

## How do I fix CVE-2018-18646?

Upgrade to a fixed version.

## Is CVE-2018-18646 being exploited?

There is no known exploitation of CVE-2018-18646 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-2018-18646 and fix it if it is affected.

What it is: CVE-2018-18646 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 4 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18646 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-2018-18646/ (Markdown: https://insights.sbomify.com/CVE-2018-18646/index.md)
```

## Sources

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

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