GitLab: Exposed Dangerous Method or Function
CVE-2026-5173 is a high-severity exposed dangerous method or function vulnerability in GitLab, with a CVSS 3.1 base score of 8.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 18.8.9, 18.9.5, 18.10.3 as the first without the flaw, so updating GitLab to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.43% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GitLab to 18.8.9 or 18.9.5 or 18.10.3, whichever matches your release line, or a later version.
- Read the advisory on about.gitlab.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | 16.9.6 up to, but not including, 18.8.9; 18.9 up to, but not including, 18.9.5; 18.10 up to, but not including, 18.10.3 | 18.8.9, 18.9.5, 18.10.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N. Scored by CNA (gitlab.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposed Dangerous Method or Function
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
How developers prevent this class of flaw
- If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
- Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users restricted to a small set of privileged users prevented from being directly accessible at all Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.
More Exposed Dangerous Method or Function vulnerabilities (CWE-749)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in GitLab
- 7.1 High severity
- 8.2 High severity
- 7.5 High severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.3 High severity
Recent Exposed Dangerous Method or Function vulnerabilities
- 8.1 High severity
- 9.9 Critical severity
- 9.9 Critical severity
- 8.1 High severity
- 7.5 High severity
- 9.6 Critical severity
Spotted an error? Tell us.