Repository navigation
This release rebuilds the viewer UI on Angular 22.2.6. Security scanners such as OWASP ZAP report Angular 19.1.7, which 26.9.1 and earlier versions ship, as a vulnerable JavaScript library with six known vulnerabilities. The release also adds page rotation and a dark theme to the viewer, and updates the rendering engine to GroupDocs.Viewer 26.10.0. Upgrading is strongly recommended for every application that shows the viewer UI.
🔒 Security fixes
Update all GroupDocs.Viewer.UI.* packages to 26.10.0. The fix is in GroupDocs.Viewer.UI:
| Issue | Affected applications | Fixed in |
|---|---|---|
| The viewer UI is built with Angular 19.1.7, which has six known vulnerabilities and which security scanners report as a vulnerable JavaScript library (CWE-1395) | applications that show the viewer UI with MapGroupDocsViewerUI |
GroupDocs.Viewer.UI |
The viewer UI is built with Angular 22.2.6
GroupDocs.Viewer.UI 26.9.1 and earlier embed a viewer UI built with Angular 19.1.7, which is affected by these vulnerabilities:
- CVE-2026-54267, high severity: DOM clobbering and response cache poisoning in client hydration.
- CVE-2026-32635, high severity: cross-site scripting in i18n attribute bindings.
- CVE-2026-27970, high severity: cross-site scripting in i18n.
- CVE-2026-88057, moderate severity: sanitization bypass through directive host bindings.
- CVE-2026-50557, moderate severity: sanitization bypass through template and attribute namespaces.
- CVE-2026-52725, moderate severity: sanitization bypass through template and dynamic component namespaces.
Angular has no patched 19.x release, the fixes are in Angular 20.3.28, 21.2.20, and 22.1.0. The viewer UI in 26.10.0 is built with Angular 22.2.6, and none of the packages bundled into it has a known vulnerability at the time of release. Scanners read the Angular version from the ng-version attribute of the page, so with 26.10.0 they find 22.2.6.
If you can't upgrade right away
The vulnerable code is part of the UI embedded in GroupDocs.Viewer.UI, so there is no configuration workaround. Upgrade.
⚠️ Behavior changes
- New buttons in the UI. The toolbar has buttons that rotate pages, and the header has a button that switches between the light and dark themes. Both are visible by default. To hide them, set
EnableRotateandEnableThemeSwitchertofalse, see below. - Users can switch to the dark theme. The viewer still opens in the light theme. The browser remembers the theme a user picks with the theme button and uses it the next time the viewer opens.
- Custom brand colors don't fully apply to the dark theme. The dark theme sets its own colors, and a plain
:rootrule in a stylesheet added withAddCustomStylesheet()loses to them when the operating system is set to dark. Add dark-theme values under:root[data-theme="dark"], or hide the theme button, see Override brand colors. - The logo text is drawn in the text color of the theme. The header uses only the shape of the image set with
SetLogoText()and paints it in the text color of the current theme, so the logo text shows in both themes. The colors of the image are no longer used. - The markup and styles of the UI changed. If your stylesheet targets elements of the UI, for example
.gd-header-app, check it in both themes. - Thumbnails appear after their pages. The viewer API renders a thumbnail when the browser asks for it, instead of before it returns the pages, see Thumbnails no longer hold up the pages.
- The rendering engine uses SkiaSharp 4. If your project references SkiaSharp 3.x itself, the restore fails with
NU1605(package downgrade) until you update the reference to 4.152.1 or later, see Rendering engine updated to GroupDocs.Viewer 26.10.0.
🛠️ Other changes
Rendering engine updated to GroupDocs.Viewer 26.10.0
GroupDocs.Viewer 26.10 adds engine builds for .NET 8 and .NET 10. Applications on .NET 8 and .NET 10 now render with these builds instead of the .NET 6 build, and applications on .NET 6 keep the .NET 6 build. The release fixes rendering of DXF drawings, MSG and other email messages, a DOCX file that failed with a null reference exception, SVG images on Linux, and PDF to HTML: missing text, missing spaces between words, and an exception. See the GroupDocs.Viewer for .NET 26.10 release notes for details.
The engine adds two options, both off by default. Set them with ConfigureHtmlViewOptions:
PdfOptions.FixThaiMarksfixes Thai marks that end up stranded when a PDF document is rendered to HTML with embedded resources, the default of the viewer. It can slow rendering down significantly.CadOptions.EnableLayeredRenderingrenders each layer of a CAD drawing to HTML as a group with the layer name as itsid.
builder.Services
.AddControllers()
.AddGroupDocsViewerSelfHostApi(config =>
{
config.ConfigureHtmlViewOptions(options =>
{
options.PdfOptions.FixThaiMarks = true;
});
});The dependencies of the engine changed:
- SkiaSharp 4.152.1 instead of 3.119.2. If your project references SkiaSharp itself, update the reference to 4.152.1 or later. With an older version, the restore fails with
NU1605. - System.Security.Cryptography.Pkcs: the engine now depends on the patched versions itself, 8.0.2 on .NET 6 and .NET 8 and 9.0.21 on .NET 10.
GroupDocs.Viewer.UI.SelfHost.Apino longer references this package orSystem.Formats.Asn1directly. On .NET 10, applications now get 9.0.21 instead of the 10.0.13 that 26.9.1 referenced. Both versions have the fixes.
PSD, PSB, AI, and ONE documents are still not rendered by the cross-platform engine builds, as described in the 26.8.0 release notes.
Updated dependencies
GroupDocs.Viewer.UI.Api.AzureBlob.Storageuses Azure.Storage.Blobs 12.30.1 instead of 12.27.0. It brings Azure.Core 1.60, which requires System.Text.Json 10.0.9 or later and adds Microsoft.Identity.Client to its dependencies, so the package no longer references System.Text.Json 8.0.6 itself. Applications on .NET 6 and .NET 8 that use it now get System.Text.Json 10.GroupDocs.Viewer.UI.Api.AwsS3.Storageuses AWSSDK.S3 4.0.104.12 instead of 4.0.22.1. It stays on AWS SDK 4.0: version 4.1 has no build for .NET 6, and its dependencies add build warnings on .NET 6 and .NET 8.- On .NET 10,
GroupDocs.Viewer.UI.Api.Distributed.CacheandGroupDocs.Viewer.UI.Api.InMemory.Cachedepend on the 10.0.15 versions of their Microsoft.Extensions packages instead of 10.0.7.
Rotate pages
The rotate buttons in the toolbar turn all pages 90 degrees clockwise or counterclockwise, and so do the Cmd/Ctrl + Shift + + and Cmd/Ctrl + Shift + - keyboard shortcuts. To hide the buttons and turn off the shortcuts, set EnableRotate to false:
builder.Services
.AddGroupDocsViewerUI(config =>
{
config.EnableRotate = false;
});Light and dark themes
The viewer has a light and a dark theme, and a button in the header that switches between them. Two new settings control them:
EnableThemeSwitchershows or hides the theme button. Default value:true.DefaultThemesets the theme the viewer opens with:Theme.Light(default),Theme.Dark, orTheme.Auto, which follows the light or dark setting of the operating system.
Once a user picks a theme with the theme button, the browser remembers that choice and uses it instead of DefaultTheme. When the theme button is hidden, the viewer always opens in DefaultTheme.
using GroupDocs.Viewer.UI.Core.Configuration;
builder.Services
.AddGroupDocsViewerUI(config =>
{
config.DefaultTheme = Theme.Auto; // Follow the operating system
});EnableRotate and EnableThemeSwitcher can also be set in the GroupDocsViewerUI section of the configuration, for example in appsettings.json.
Translations are separate files
The UI now loads its translations from assets/i18n/<language>.json under UIPath, and the language list shows the flag of each language. MapGroupDocsViewerUI serves these files like the rest of the UI, so conventions such as RequireAuthorization() apply to them. If a proxy in front of your application allows only known UI files, allow these too.
Thumbnails no longer hold up the pages
The viewer API rendered the thumbnails of the pages it creates before it answered view-data and create-pages, and a thumbnail often takes longer to render than its page. Now the API returns the thumbnail URLs right away and renders each thumbnail when the browser requests it with get-thumb. With the documents of the new performance sample, the next pages came 38% to 86% sooner, and the first response up to 40% sooner. A thumbnail that isn't in the cache yet appears a moment after its page.
The search bar covers the toolbar buttons
When the search bar opened, the search button and the edge of the Print button stayed visible next to it. The search bar now covers all the toolbar buttons.
ConfigurePdfViewOptions applies PdfOptimizationOptions
The PDF that the viewer creates for download and printing ignored the PdfOptimizationOptions set with ConfigurePdfViewOptions. It now uses them, for example to turn on OptimizeSpreadsheets, which makes the PDF of a large sheet smaller and quicker to create:
using GroupDocs.Viewer.Options;
builder.Services
.AddControllers()
.AddGroupDocsViewerSelfHostApi(config =>
{
config.ConfigurePdfViewOptions(options =>
{
options.PdfOptimizationOptions = new PdfOptimizationOptions { OptimizeSpreadsheets = true };
});
});New sample: performance tuning
The new GroupDocs.Viewer.UI.Sample.Performance sample shows settings that make the viewer faster and the pages it sends smaller:
PreloadPages = 1: the first response waits for one rendered page instead of three.ExcludeFonts: the HTML pages are sent without fonts, which every page would otherwise embed again.SpreadsheetOptions.ForSplitSheetIntoPages(100): the first page of a large sheet no longer waits for the whole sheet, which is one page by default.DefaultFontNameon Linux, where servers usually don't have the fonts that documents use.- The PDF for download and printing uses the sheets' page breaks and
OptimizeSpreadsheets. - The local cache, response compression, and a warm-up of the rendering engine when the app starts.
With the sample's documents, the 13 slides of a presentation take 97% less data, and the first page of a 10,000-row sheet takes 99% less data and 59% less time. Every API request logs its time and sends it in the Server-Timing header, so you can compare the settings with your own documents.
Samples run on .NET 10 and start the same way
- All samples target .NET 10.
- Every web sample opens at
https://localhost:5001andhttp://localhost:5000. The API service of the two-app sample,GroupDocs.Viewer.UI.SelfHost.Api.Service.Sample, runs athttps://localhost:5003andhttp://localhost:5002, so both apps run at the same time. The launch settings are now part of the repository. - The start pages of all samples share one design, and the Authorization sample uses it for its own pages.
- The Dockerfiles use the .NET 10 images and expose port 8080, the port the app listens on in the container. Published samples now include their start page, which returned an error in a container before.
- The custom branding sample brands the dark theme as well.
📦 Packages
All GroupDocs.Viewer.UI packages are available on NuGet at version 26.10.0:
- GroupDocs.Viewer.UI
- GroupDocs.Viewer.UI.Api
- GroupDocs.Viewer.UI.Api.AwsS3.Storage
- GroupDocs.Viewer.UI.Api.AzureBlob.Storage
- GroupDocs.Viewer.UI.Api.Cloud.Storage
- GroupDocs.Viewer.UI.Api.Distributed.Cache
- GroupDocs.Viewer.UI.Api.InMemory.Cache
- GroupDocs.Viewer.UI.Api.Local.Cache
- GroupDocs.Viewer.UI.Api.Local.Storage
- GroupDocs.Viewer.UI.Cloud.Api
- GroupDocs.Viewer.UI.Core
- GroupDocs.Viewer.UI.SelfHost.Api
Thank you for using GroupDocs.Viewer.UI! If you encounter any issues or have suggestions, please don't hesitate to provide feedback here on GitHub or at our Free Support Forum.