Authenticated SSRF via webhook header CRLF injection
Published Sep 12, 2025 · Updated Sep 12, 2025
Server-side request forgery in GitLab CE/EE allows remote authenticated users to reach internal services through webhook requests. Webhook custom-header names accept CRLF sequences, causing an outbound proxy to parse attacker-controlled header data as a second HTTP request. A configured forward proxy that permits HTTP pipelining is required, and the resulting access is blind rather than direct response disclosure.
Summary
What happened
Server-side request forgery in GitLab CE/EE allows remote authenticated users to reach internal services through webhook requests. Webhook custom-header names accept CRLF sequences, causing an outbound proxy to parse attacker-controlled header data as a second HTTP request. A configured forward proxy that permits HTTP pipelining is required, and the resulting access is blind rather than direct response disclosure.
The record
- CVE
- CVE-2025-6454
- Published
- Sep 12, 2025
- Updated
- Sep 12, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 12, 2025CVE publishedPublication date reported by the CVE source.
- Sep 12, 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=16.11 <18.1.6
- Affected versionversion=18.2 <18.2.6
- Affected versionversion=18.3 <18.3.2
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
- GitLab webhook CRLF blind SSRF reproductionproof of concept · demonstrated
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