Account takeover via injected Network Error Logging headers
Published Apr 24, 2025 · Updated Apr 24, 2025
NEL header injection in GitLab CE and EE allows remote authenticated users to track browsing activity and take over accounts. GitLab identifies the Maven Dependency Proxy as the locus but has not disclosed which response-building operation accepts the injected header. Exploitation requires low-privileged access, a high-complexity setup, and user interaction; the resulting browser telemetry can expose activity and enable account takeover.
Summary
What happened
NEL header injection in GitLab CE and EE allows remote authenticated users to track browsing activity and take over accounts. GitLab identifies the Maven Dependency Proxy as the locus but has not disclosed which response-building operation accepts the injected header. Exploitation requires low-privileged access, a high-complexity setup, and user interaction; the resulting browser telemetry can expose activity and enable account takeover.
The record
- CVE
- CVE-2025-1908
- Published
- Apr 24, 2025
- Updated
- Apr 24, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-840
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2025CVE publishedPublication date reported by the CVE source.
- Apr 24, 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.6 <17.9.7
- Affected versionversion=17.10 <17.10.5
- Affected versionversion=17.11 <17.11.1
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