GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.8 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an unauthenticated user to cause denial of service by sending repeated GraphQL queries.
CVE-2025-8099
HIGHNVD 7.5
7.5
- CVSS v3
- 7.5
- EG Score
- —
- EPSS
- —
- KEV
- Not listed
Published
February 11, 2026
Last Modified
February 13, 2026
References (3)
Vendor Advisories for CVE-2025-8099(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-8099?
CVE-2025-8099 is a high vulnerability published on February 11, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.8 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an unauthenticated user to cause denial of service by sending repeated GraphQL queries.
When was CVE-2025-8099 disclosed?
CVE-2025-8099 was first published in the National Vulnerability Database on February 11, 2026, with the most recent update on February 13, 2026. 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-8099?
CVE-2025-8099 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-8099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-8099, 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-8099
Is Your Infrastructure Affected by CVE-2025-8099?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.