Browser script execution via proxy cache headers
Published Jun 20, 2025 · Updated Jun 20, 2025
Cross-site scripting in GitLab EE allows remote authenticated users to run scripts in another user's browser through Maven proxy cache headers. The public advisory identifies the Maven Dependency Proxy cache-header path but does not disclose which header or sanitization operation permits the CSP bypass. Exploitation requires low-privileged access and user interaction and affects 16.6 through 17.9.6, 17.10 through 17.10.4, and 17.11.0.
Summary
What happened
Cross-site scripting in GitLab EE allows remote authenticated users to run scripts in another user's browser through Maven proxy cache headers. The public advisory identifies the Maven Dependency Proxy cache-header path but does not disclose which header or sanitization operation permits the CSP bypass. Exploitation requires low-privileged access and user interaction and affects 16.6 through 17.9.6, 17.10 through 17.10.4, and 17.11.0.
The record
- CVE
- CVE-2025-2443
- Published
- Jun 20, 2025
- Updated
- Jun 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, CAPEC-63, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 20, 2025CVE publishedPublication date reported by the CVE source.
- Jun 20, 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