# CVE-2025-2045: Incorrect Authorization in GitLab

> Users with limited permissions can access sensitive project analytics data in GitLab Enterprise Edition due to improper authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2025
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-2cg5-9vjw-w6vg

## What is CVE-2025-2045?

CVE-2025-2045 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 6 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper authorization in GitLab EE affecting all versions from 17.7 prior to 17.7.6, 17.8 prior to 17.8.4, 17.9 prior to 17.9.1  allow users with limited permissions to access to potentially sensitive project analytics data.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-2045?

It affects 1 product.


Products: Gitlab Gitlab.

## How do I fix CVE-2025-2045?

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

## Is CVE-2025-2045 being exploited?

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

What it is: CVE-2025-2045 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 6 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2045 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-2025-2045/ (Markdown: https://insights.sbomify.com/CVE-2025-2045/index.md)
```

## Sources

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

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