CVE-2025-8279: GitLab Language Server · Missing Authentication
Affects GitLab Language ServerSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 7.30.0 soon.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.30.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade GitLab Language Server to 7.30.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitLab GitLab Language Server | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-8279, European organizations should immediately assess their GitLab Language Server versions and upgrade to version 7.30.0 or later where the vulnerability is patched. Until patching is possible, organizations should restrict network access to the GitLab Language Server, limiting exposure to trusted internal networks and using firewall rules or VPNs to prevent unauthorized external access. Implementing strict network segmentation and monitoring for unusual GraphQL query patterns can help detect exploitation attempts. Additionally, organizations should review and harden authentication and authorization configurations around GitLab services, ensuring that only authorized users and systems can interact with critical functions. Employing Web Application Firewalls (WAFs) with custom rules to detect and block suspicious GraphQL queries may provide an additional layer of defense. Regularly auditing logs for anomalous activity related to GraphQL endpoints and integrating these alerts into Security Information and Event Management (SIEM) systems will improve incident detection and response capabilities. Finally, organizations should educate development and security teams about this vulnerability and incorporate it into their vulnerability management and patching workflows to prevent future exposure.
Description
Insufficient input validation within GitLab Language Server 7.6.0 and later before 7.30.0 allows arbitrary GraphQL query execution