Cross-site scripting via unintended proxy rendering
Published Jul 23, 2025 · Updated Feb 26, 2026
Cross-site scripting in GitLab CE/EE 15.10 through 18.0.4, 18.1 through 18.1.2, and 18.2 allows remote authenticated users to run scripts. The Kubernetes Proxy performs unintended content rendering, but GitLab has not published the responsible code locus or input-handling error. Exploitation requires low-privileged access and victim interaction, exposing or modifying data in the victim's browser context.
Summary
What happened
Cross-site scripting in GitLab CE/EE 15.10 through 18.0.4, 18.1 through 18.1.2, and 18.2 allows remote authenticated users to run scripts. The Kubernetes Proxy performs unintended content rendering, but GitLab has not published the responsible code locus or input-handling error. Exploitation requires low-privileged access and victim interaction, exposing or modifying data in the victim's browser context.
The record
- CVE
- CVE-2025-4700
- Published
- Jul 23, 2025
- Updated
- Feb 26, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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=15.10 <18.0.5
- Affected versionversion=18.1 <18.1.3
- Affected versionversion=18.2 <18.2.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