lakeFS vulnerable to Arbitrary JavaScript Injection via Direct Link to HTML Files
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Impact The browser renders the resulting HTML when opening a direct link to an HTML file via lakeFS. Any JavaScript within that page is executed within the context of the domain lakeFS is running in. An attacker can inject a malicious script inline, download resources from another domain, or make arbitrary HTTP requests. This would allow the attacker to send information to a random domain or carry out lakeFS operations while impersonating the victim. Note that to carry out this attack, an attacker must already have access to upload the malicious HTML file to one or more repositories. It also depends on the victim receiving and opening the link to the malicious HTML file. ### Patches This is fixed in lakeFS version 0.106.0 ### Workarounds There are no known workarounds at this time.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/treeverse/lakefs (Go) | before 0.106.0 | 0.106.0 | Patch available | GHSA-9phh-r37v-34wh |
- github.com/treeverse/lakefs (Go) Vendor— Affected before 0.106.0 Fixed in 0.106.0 Patch available GHSA-9phh-r37v-34wh
Remediation
- Fix · GHSA-9phh-r37v-34wh github.com/treeverse/lakefs (Go) Fixed in 0.106.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-9phh-r37v-34wh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences