Skip to main content
Version: 4.1 (2026 H2)

Release 4.1.10085.0 (October 2026)

Release 4.1.10085.0 is a maintenance release for Release 4.1.10084.0. It was prompted by a Microsoft security update for Windows authentication in ASP.NET Core that should not wait for the next release. It also includes selected fixes completed since Release 4.1.10084.0.

Security update CVE-2026-70179​

On 13 October 2026, Microsoft published vulnerability CVE-2026-70179 in the Microsoft.AspNetCore.Authentication.Negotiate package and rated it high. The package provides the Windows authentication used by several primedocs server applications. The vulnerability can only be exploited when claims resolution via LDAP is enabled. primedocs does not enable this feature. Security scanners nevertheless report the affected version.

Release 4.1.10085.0 ships the fixed version 10.0.13 and also moves the other packages of the same .NET servicing release from 10.0.12 to 10.0.13. The update is recommended for all installations.

All changes​

Web app​

Improved

  • Notice when a profile is missing. If a template requires a profile with a shared organizational unit and none is available, the web app shows the full notice with the link «Open User & Profiles». The form stays locked until then and is released without reloading as soon as a suitable profile has been created or adjusted.

Fixed

  • Selection message for ObjectCollection with SelectedObjectId. The message «An entry has to be selected.» now only appears when the selection is actually missing. A configured ValidationMessage takes precedence.

Web Admin​

Fixed

  • Moving an organizational unit. After a move, the organizational unit detail immediately shows the newly inherited values.

Office add-ins​

Fixed

  • Signature without a matching campaign. If no campaign matches a campaign field, the signature is still created, with an empty campaign area.
  • Special characters in Outlook templates. Placeholders in the subject, recipients and plain-text messages keep characters such as & and < as they are instead of inserting them as HTML code (&amp;).

Administration​

Fixed

  • Dependency analysis during package export. Templates with the Dispatch Manager no longer wrongly report a missing Forms function during export.

Integration and interfaces​

Improved

  • Connect without the developer error page. After the update, Connect runs as a production environment. Unhandled errors no longer show a developer error page with technical details.

Fixed

  • Stored Microsoft 365 sign-in is kept. If renewing the sign-in fails while saving to OneDrive, SharePoint or Teams, the stored sign-in is kept. Saving fails with an error message, and the cause is written to the server log. Previously, the sign-in was deleted in this case.

Desktop client​

Fixed

  • Organizational unit permissions when saving templates. If a template only has permissions for organizational units and none for users or groups, they are kept when saving in the desktop client. The fix takes effect with the update of the server applications. As before, the user who saves is added with permissions as well. Permissions that were already lost must be set again.
  • Template selection with a missing tag. If a template refers to a tag that is not available in the desktop client (deleted, not visible or not synchronized yet), the template selection still opens. The same applies to a missing template group.
  • Series as PDF from PowerPoint. The «Save as PDF» option in the series creation dialog now also works for PowerPoint templates.
  • Closing «Configuration test» with Esc. The «Configuration test» window can now be closed with Esc.

Operations and installation​

Improved

  • No telemetry from Syncfusion components. Telemetry of the Syncfusion libraries used by primedocs is switched off in the desktop client and on the server.

Important notices​

Update the server applications

The security update is part of the primedocs server applications. The .NET 10 Windows Hosting Bundle does not need to be updated for it. Details: Update primedocs server.

Check the Connect configuration

The update replaces the web.config in the Connect folder. If the previous web.config was carried over manually, remove the ASPNETCORE_ENVIRONMENT entry with the value Development there. For troubleshooting an HTTP 500 error without details: Troubleshooting.