# CVE-2026-115736: Authorization Bypass Through User-Controlled Key in GitLab


- **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
- **Fix available:** Yes
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-4877-j5r3-5v2r

## What is CVE-2026-115736?

CVE-2026-115736 is a medium-severity vulnerability in GitLab, published on 17 Nov 2026. 

### Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to view unredacted secret values from secret detection findings they had access to through GitLab Duo Agent Platform due to improper authorization checks.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-115736?

It affects 1 product.


Products: GitLab.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*` from 19.1 before 19.3.9
- `cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*` from 19.4 before 19.4.8
- `cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*` from 19.5 before 19.5.6

## How do I fix CVE-2026-115736?

Upgrade GitLab to the fixed version for your release line. The advisory names 19.3.9, 19.4, 19.4.8 and 19.5.

## Is CVE-2026-115736 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115736 and fix it if it is affected.

What it is: CVE-2026-115736 is a medium-severity vulnerability in GitLab, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-115736 in the wild and no public exploit code.

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

## Sources

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

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