# CVE-2026-84284: GitLab incorrect authorization in work items GraphQL API

Source: https://junglewise.ai/threats/cve-2026-84284-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-13. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-84284 · Severity: medium · CVSS 5.3 · Published 2026-10-13

GitLab Community Edition and Enterprise Edition contains an authorization flaw that allows unauthenticated users to read work item contents from private groups and projects. An attacker can exploit this to view sensitive project data without credentials or access permissions.

Technologies: [GitLab Community Edition](https://junglewise.ai/threats/technologies/gitlab-ce), [GitLab Enterprise Edition](https://junglewise.ai/threats/technologies/gitlab-ee), [GitLab](https://junglewise.ai/threats/technologies/gitlab). Vendors: [GitLab](https://junglewise.ai/threats/vendors/gitlab).

## Quick answers

**Is CVE-2026-84284 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-84284 being exploited in the wild.

**How severe is CVE-2026-84284?** Medium severity, with a CVSS score of 5.3, published 13 October 2026.

**Which products and versions are affected?** GitLab Community Edition 17.11 before 19.2.8, all 19.3, 19.4 before 19.4.2; GitLab Enterprise Edition 17.11 before 19.2.8, all 19.3, 19.4 before 19.4.2.

**Is there a fix for CVE-2026-84284?** Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-84284 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-84284?** Check whether you run GitLab Community Edition, GitLab Enterprise Edition or GitLab at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2

## Technical details

The vulnerability is an incorrect authorization issue in the GraphQL work items API that fails to properly validate user permissions before returning work item data. Unauthenticated attackers can read work item contents from private groups and projects due to insufficient authorization checks. The flaw affects versions 17.11 through 19.2.7, all 19.3.x versions, and 19.4.0–19.4.1.

## Affected products

- GitLab Community Edition 17.11 before 19.2.8, all 19.3, 19.4 before 19.4.2
- GitLab Enterprise Edition 17.11 before 19.2.8, all 19.3, 19.4 before 19.4.2

## Timeline

- 2026-10-13: disclosed
- 2026-10-12: patched

## References

- [https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/)
- [https://gitlab.com/gitlab-org/gitlab/-/work_items/627167](https://gitlab.com/gitlab-org/gitlab/-/work_items/627167)

## Related threats

- [GitLab authentication bypass in OmniAuth SAML/LDAP auto-linking](https://junglewise.ai/threats/cve-2026-15723-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab Enterprise Edition authorization bypass in billing validation](https://junglewise.ai/threats/cve-2026-112378-gitlab-has-remediated-an-issue-in-gitlab-ee-affecting-all)
- [GitLab CE/EE internal credential exposure in response headers](https://junglewise.ai/threats/cve-2026-105777-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab has remediated an issue in GitLab EE affecting all versions from 13.6 before 19.2.8, 19.3 before 19.3.5, and…](https://junglewise.ai/threats/cve-2026-9268-gitlab-has-remediated-an-issue-in-gitlab-ee-affecting-all-versions)
- [GitLab CE/EE integer overflow in CI/CD regular expression compiler](https://junglewise.ai/threats/cve-2026-97229-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
