dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-62378

CRITICAL · 9.0 CVSS v3.1 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RustFS Console is a web management console for the RustFS distributed file system. From 0.1.7 until 0.1.10, the RustFS Console components/object/preview-modal.tsx and components/object/pdf-viewer.tsx extension-based PDF preview path can render HTML content uploaded as .pdf, allowing stored cross-site scripting in the management console and exposure of administrator AccessKeyId, SecretAccessKey, and SessionToken values. This is caused by a regression of CVE-2026-27822. This vulnerability is fixed in 0.1.10.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RustFS Console PDF preview feature in versions 0.1.7-0.1.10 uses file extension-based content type detection in preview-modal.tsx and pdf-viewer.tsx. Attackers can upload HTML files renamed to .pdf, which the preview function then renders as executable HTML, enabling stored XSS that can exfiltrate administrator AWS credentials (AccessKeyId, SecretAccessKey, SessionToken). This is a regression of CVE-2026-27822.

MitigationUpgrade to version 0.1.10 or later. Additionally, implement server-side content-type validation and MIME-type checking rather than relying on file extensions to prevent HTML execution in PDF previews.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify RustFS Console version
    Check the installed package version of RustFS Console (package.json, Cargo.toml, or running 'rustfs --version' or similar)
    Affected if Version is 0.1.7, 0.1.8, 0.1.9, or 0.1.10 (the affected range)
  2. Confirm PDF preview feature is enabled
    Determine if the PDF preview feature in the console is accessible to users (check console configuration or feature flags)
    Affected if The PDF preview modal functionality is available and users can trigger file previews
  3. Inspect preview-modal.tsx for extension-based detection
    Locate and examine the file preview-modal.tsx in the source code; look for logic that determines content type based solely on file extension (e.g., checking .pdf extension without MIME type validation)
    Affected if Code uses only file extension to determine content type for PDF previews
  4. Inspect pdf-viewer.tsx for extension-based detection
    Locate and examine the file pdf-viewer.tsx in the source code; look for logic that renders content based on file extension without validating actual MIME type
    Affected if Code uses only file extension to determine how to render uploaded files
  5. Check for absence of server-side MIME validation
    Review the file upload handler or API endpoint that processes uploaded files; verify whether server-side content-type or MIME-type validation is performed before rendering
    Affected if Server does not validate actual file content type/MIME type and relies only on client-side extension checking

Environment is affected if RustFS Console version is 0.1.7 through 0.1.10 and the PDF preview feature is enabled, with source code showing extension-only content type detection in preview-modal.tsx or pdf-viewer.tsx lacking server-side MIME validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.1.10 or later. Additionally, implement server-side content-type validation and MIME-type checking rather than relying on file extensions to prevent HTML execution in PDF previews.

Recommended fix High confidence

0.1.10

  1. Upgrade RustFS Console to version 0.1.10 or later to resolve the stored XSS vulnerability in the PDF preview components

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-62378 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data