--- title: "Version 5.11 (December 2025)" slug: "dpgw-release-notes-5-11" updated: 2026-03-27T11:01:04Z published: 2026-03-27T11:01:04Z canonical: "docs.onespan.com/dpgw-release-notes-5-11" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Version 5.11 (December 2025) ## New features and enhancements Upgrade path DIGIPASS Gateway supports direct upgrades from version 5.10 to version 5.11 on the supported operating systems. Supported platforms, database management systems, and other third-party products Operating systems Installation packages are now included for the following: - Windows Server 2025, 64-bit Software libraries The software library lists are not exhaustive and include the most significant and security-relevant updates only. CVE references are provided for informational purposes only and do not imply that the corresponding vulnerabilities were exploitable in the product. For a complete overview, refer to the third-party dependency files included with the installed product. This version now includes the following (updated) third-party libraries: - Apache Commons Lang 3.19.0 Fixes: [CVE-2025-48924](https://www.cve.org/CVERecord?id=CVE-2025-48924) - Netty/Codec/HTTP 4.1.128.Final Fixes: [CVE-2025-58057](https://www.cve.org/CVERecord?id=CVE-2025-58057), [CVE-2025-58056](https://www.cve.org/CVERecord?id=CVE-2025-58056) - Netty/Codec/HTTP2 4.1.128.Final Fixes: [CVE-2025-58057](https://www.cve.org/CVERecord?id=CVE-2025-58057), [CVE-2025-55163](https://www.cve.org/CVERecord?id=CVE-2025-55163) - Spring Beans 6.2.11 Fixes: [CVE-2025-41242](https://www.cve.org/CVERecord?id=CVE-2025-41242) - Spring Core 6.2.11 Fixes: [CVE-2025-41249](https://www.cve.org/CVERecord?id=CVE-2025-41249) - Spring Security 6.5.5 Fixes: [CVE-2025-41232](https://www.cve.org/CVERecord?id=CVE-2025-41232), [CVE-2025-41248](https://www.cve.org/CVERecord?id=CVE-2025-41248) Web servers DIGIPASS Gateway can now be run on the following web application servers (based on the respective JRE): - Apache Tomcat 10.1.48 (included) Fixes: [CVE-2025-48989](https://www.cve.org/CVERecord?id=CVE-2025-48989), [CVE-2025-31651](https://www.cve.org/CVERecord?id=CVE-2025-31651), [CVE-2025-31650](https://www.cve.org/CVERecord?id=CVE-2025-31650), [CVE-2025-24813](https://www.cve.org/CVERecord?id=CVE-2025-24813) - Oracle Server JRE 17 - Azul Zulu 17 (17.62.17 included **NEW** ) ## Fixes and other updates Issue OAS-27871 (Support case CS0184113): Antivirus software impacts DIGIPASS Gateway Description: Running DIGIPASS Gateway and antivirus applications on the same host can negatively impact overall system performance. Under some circumstances, the DIGIPASS Gateway service can even be falsely identified as malware and blocked by certain antivirus applications. Status: Third-party antivirus and antimalware software can interfere with DIGIPASS Gateway and prevent it from working correctly, especially when deployed using the provided installation packages that already include an Apache Tomcat web server. To prevent issues, the DIGIPASS Gateway installation folder should be added to the exclusion list of the interfering antivirus software. The documentation was extended to include respective information. ## Deprecated components and features PDF documentation The PDF documentation has been completely removed from the DIGIPASS Gateway product deliverable. You can view the DIGIPASS Gateway user documentation exclusively online on the OneSpan documentation portal, available at [https://docs.onespan.com/sec/docs/digipass-gateway](https://docs.onespan.com/sec/docs/digipass-gateway). Supported platforms, data management systems, and other third-party products Operating systems Installation packages are no longer included for the following: - Red Hat Enterprise Linux (RHEL) 7, 64-bit - Ubuntu Server 18.04 LTS, 64-bit ## Known issues Issue OAS-7063 (Support case CS0049841): FQDN cannot start with number Description: DIGIPASS Gateway cannot be installed if the fully qualified domain name (FQDN) of the server starts with a number, e.g. 001234-MYHOST. In that case, the setup will issue an error when it attempts to generate a self-signed certificate for the Apache Tomcat web server. Status: No fix available. To circumvent this issue ensure that the FQDN meets the naming requirements before you install DIGIPASS Gateway. Issue OAS-4908 (Support case CS0024103): Certificate must contain IP address when using FQDN Description: If you use the FQDN to connect to the OneSpan Authentication Server instance, the respective server certificate for SOAP connections must specify the IP address of the OneSpan Authentication Server instance either as common name (CN) or the subject alternative name (SAN). Otherwise, this can cause a "No subject alternative name matching IP address" error message during the setup, indicating that DIGIPASS Gateway verifies the SAN in the OneSpan Authentication Server certificate but does not find any matching IP address. Status: No fix available. The OneSpan Authentication Server IP address must be set either as common name (CN) or the subject alternative name (SAN) in the certificate. For more information, see [KB0014260](https://support.onespan.com/csm?id=kb_article_view&sysparm_article=KB0014260). SSL certificate selection from network repository Description: With the current version of the DIGIPASS Gateway installer, it is not possible to select the OneSpan Authentication Server SOAP certificate if it is located on a network drive. Status: No fix available. To circumvent this issue the certificate must first be copied locally before being selected when installing DIGIPASS Gateway.