oxyno-zeta/s3-proxy is an aws s3 proxy written in go. In affected versions a Reflected Cross-site Scripting…
Historical advisory recorded 25 Oct 2026 02:24:42 UTC. Read the latest advisory.
nvd · CVE-2025-27088
Publishedoxyno-zeta/s3-proxy is an aws s3 proxy written in go. In affected versions a Reflected Cross-site Scripting (XSS) vulnerability enables attackers to create malicious URLs that, when visited, inject scripts into the web application. This can lead to session hijacking or phishing attacks on a trusted domain, posing a moderate risk to all users. It's possible to inject html elements, including scripts through the folder-list template. The affected template allows users to interact with the URL path provided by the `Request.URL.Path` variable, which is then rendered directly into the HTML without proper sanitization or escaping. This can be abused by attackers who craft a malicious URL containing injected HTML or JavaScript. When users visit such a URL, the malicious script will be executed in the user's context. This issue has been addressed in version 4.18.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2025-27088
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-79
Original publisher date fields
published: 2025-02-20T23:15:13.397
lastModified: 2026-06-17T09:03:00.583
3 source CPE criteria · context only
- cpe:2.3:a:oxyno-zeta:s3-proxy:*:*:*:*:*:helm:*:*
- cpe:2.3:a:oxyno-zeta:s3-proxy:*:*:*:*:*:docker:*:*
- cpe:2.3:a:oxyno-zeta:s3-proxy:*:*:*:*:*:go:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON