GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.7 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2, that could have allowed a blocked user to access sensitive information by establishing GraphQL subscriptions through WebSocket connections.
CVE-2025-2615
MEDIUMNVD 4.3
4.3
- CVSS v3
- 4.3
- EG Score
- —
- EPSS
- —
- KEV
- Not listed
Published
November 15, 2025
Last Modified
November 19, 2025
References (3)
Vendor Advisories for CVE-2025-2615(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Frequently asked(4)
What is CVE-2025-2615?
CVE-2025-2615 is a medium vulnerability published on November 15, 2025. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.7 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2, that could have allowed a blocked user to access sensitive information by establishing GraphQL subscriptions through WebSocket connections.
When was CVE-2025-2615 disclosed?
CVE-2025-2615 was first published in the National Vulnerability Database on November 15, 2025, with the most recent update on November 19, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2025-2615?
CVE-2025-2615 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2025-2615?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-2615, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-2615
Is Your Infrastructure Affected by CVE-2025-2615?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.