Skip to content
Fencer Vulns
high 8.2

CVE-2026-91127 json

File Viewer: DOM XSS via unsafe hyperlink schemes in the legacy DOC renderer

published 2026-09-18 51 d ago modified 2026-09-24 45 d ago also GHSA-3753-m2x2-q623 , EUVD-2026-83206

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

File Viewer is a browser-native viewer for Office, PDF, CAD, archive, and other files in private and internal web applications. Prior to @file-viewer/doc 2.3.1 and msdoc-viewer 0.2.2, the legacy DOC renderer emitted document-controlled hyperlink targets into generated HTML after character escaping but without restricting URL schemes. A crafted legacy DOC file could place javascript:, vbscript:, data:, or another unsafe scheme in a rendered link, and script could execute in the embedding application's origin when a user clicked the link. The fix blocks external document links by default, allows only HTTP(S), mail, telephone, safe relative URLs, and internal bookmarks when external links are explicitly enabled, and applies mount-boundary sanitization as defense in depth. This issue is fixed in @file-viewer/doc 2.3.1 and msdoc-viewer 0.2.2.

Patch / fix

  • npm @file-viewer/doc 2.3.1
  • npm msdoc-viewer 0.2.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
48 d ago

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm @file-viewer/doc
<2.3.1
2.3.1
npm msdoc-viewer
<0.2.2
0.2.2

Affected products

  • flyfish-dev file-viewer
  • @file-viewer doc
  • flyfish-dev msdoc-viewer

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-83 Improper Neutralization of Script in Attributes in a Web Page

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.