Authenticated service interruption via uncontrolled HTTP response processing
Published Jun 12, 2025 · Updated Aug 1, 2025
Resource exhaustion in GitLab CE/EE allows remote authenticated users to interrupt service through a malicious third-party integration. GitLab processes HTTP responses from an integrated third-party component without adequate input validation or resource limits. A project user must integrate an attacker-controlled component; its crafted responses can exhaust server resources and deny legitimate users access.
Summary
What happened
Resource exhaustion in GitLab CE/EE allows remote authenticated users to interrupt service through a malicious third-party integration. GitLab processes HTTP responses from an integrated third-party component without adequate input validation or resource limits. A project user must integrate an attacker-controlled component; its crafted responses can exhaust server resources and deny legitimate users access.
The record
- CVE
- CVE-2025-5996
- Published
- Jun 12, 2025
- Updated
- Aug 1, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2025CVE publishedPublication date reported by the CVE source.
- Aug 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.11 <17.11.3
- Affected versionversion=18.0 <18.0.1
- Affected versionversion=2.10 <17.10.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo