CVE-2026-27822 — rustfs
CRITICALCVE-2026-27822 is a critical-severity (CVSS 9) Cross-site Scripting (XSS) vulnerability in rustfs. A fix is available for rustfs — see the affected versions and patch details below.
Rust has Critical Stored XSS in Preview Modal, leading to Administrative Account Takeover
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27822.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-27822 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
rustfsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A Stored Cross-Site Scripting (XSS) vulnerability in the RustFS Console allows an attacker to execute arbitrary JavaScript in the context of the management console. By bypassing the PDF preview logic, an attacker can steal administrator credentials from localStorage, leading to full account takeover and system compromise.
Details
The vulnerability exists due to improper validation of the response content type during the file preview process and a lack of origin separation between the S3 object delivery and the management console.
- Origin of Credentials: The RustFS Console stores highly sensitive S3 credentials (AccessKey, SecretKey, SessionToken) in the browser's
localStorage. - Insecure Preview Implementation: In
console/components/object/preview-modal.vue, the application identifies a PDF file based on its extension or metadata and renders it using an<iframe>. - Same-Origin Vulnerability: RustFS typically hosts the management console and the S3 API on the same origin (e.g., the same IP and port).
- Bypass Attack: An attacker can upload a file named
xss.pdfbut set itsContent-Typemetadata totext/html. Because theiframeis hosted on the same origin as the console, the executed script has unrestricted access to the parent window'slocalStorage.
PoC
<img width="6006" height="3096" alt="CleanShot 2026-02-01 at 18 36 54@2x" src="https://github.com/user-attachments/assets/f2f5dae6-1e19-4133-9a69-f7d8ec604dad" />This PoC demonstrates how to steal a victim's administrative credentials by tricking them into previewing a malicious file.
1. Create the malicious payload (xss.html):
<script>
alert('XSS Success!\nLocalStorage Data: ' + JSON.stringify(window.parent.localStorage));
</script>
2. Setup the environment and upload the payload:
# 1. Create a target bucket
mc mb rustfs/my-bucket
# 2. Upload the HTML file as a PDF with HTML content type
mc cp xss.html rustfs/my-bucket/xss.pdf --attr "Content-Type=text/html"
3. Trigger the vulnerability:
- Login to the RustFS Console as an administrator.
- Navigate to
my-bucket. - Click the "Preview" button for the
xss.pdffile. - The JavaScript executes, demonstrating access to the administrative session data.
Impact
- Character: Stored Cross-Site Scripting (XSS).
- Target: System Administrators using the Console.
- Result: Full Account Takeover (ATO). An attacker gains the victim's
AccessKeyId,SecretAccessKey, andSessionToken. This allows the attacker to perform any administrative action, including deleting data, creating backdoors, or downloading the entire filesystem via the S3 API.
Proposed Mitigation
- Origin Separation: Implement a dedicated domain for data delivery (e.g.,
*.data.rustfs.io) that is different from the console domain. This leverages the Same-Origin Policy (SOP) to isolate user-uploaded content. - Security Headers: Implement strict security headers in the backend:
Content-Security-Policy (CSP): Disallow inline scripts and restrict script execution.X-Content-Type-Options: nosniff: Prevent browsers from sniffing and executing content that differs from the declared type.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | rustfs | all versions | 1.0.0-alpha.83cargo update -p rustfs --precise 1.0.0-alpha.83 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rustfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rustfs to 1.0.0-alpha.83 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27822 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27822 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-27822. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-27822 in your dependencies?
O3 Security finds CVE-2026-27822 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.