| Reference: | https://doc.wallix.com/en/bastion/12.5/rn-en-12.5.0.html |
|---|---|
| Date: | 2026-10-21 |
| Copyright: | © 2026 WALLIX |
Contents
This version includes all the improvements and new features implemented from WALLIX Bastion 12.0 and listed in the sections below.
WALLIX Bastion's real-time session supervision interface has been redesigned to provide better visibility and enhanced control.
You can now terminate sessions directly, configure automatic refresh, monitor "4 eyes/4 hands" mode sessions, and benefit from dynamic search and filtering on users, targets, protocols, and IP addresses.
WALLIX Bastion and WALLIX Access Manager now allow you to transfer files during VNC sessions on TightVNC and UltraVNC servers (up to version 1.6.4).
From WALLIX Access Manager, use the context menu to download or send files; from WALLIX Bastion, use the Ctrl+Alt+F7 shortcut to access the transfer window.
All transfers are tracked in the session video audit and can be verified through ICAP integration to strengthen your security.
Improve access to web applications through Web Session Manager to provide a smoother, more secure experience and better compatibility with a wider range of applications. New configurable parameters are now available for each web application to improve compatibility and simplify user access, notably through automatic credential injection. In addition, improve the Web Session Manager installation process to facilitate deployment and reduce friction for administration teams.
WALLIX Bastion's new audit log interface simplifies compliance tracking with extended filters allowing you to view up to 1 year of history, global search, and a detailed table by timestamp, user, client IP, action, and object.
All columns are filterable and sortable, and data can be exported to PDF for your regulatory compliance needs.
A recent Windows update causes mstsc to display a warning for any .rdp file not signed by a trusted publisher.
WALLIX Bastion now allows you to sign the RDP connection files it generates, preventing the Windows warning when they are opened with mstsc. The signing certificate is configured under Configuration / RDP file signature. The issuing certificate authority must be trusted on users’ Windows workstations.
The following features and improvements have been implemented in this version:
No improvement was part of this version.
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
Improve authentication on RDP and VNC servers by allowing the use of trusted X.509 Certificate Authorities (CA), simplifying configuration when server certificates rotate frequently.
Improve the "Named User" metric in the WALLIX licensing model to provide a more consistent and accurate view of actual usage. It now includes all primary users accessing the Bastion (local or from an IdP). The calculation is based on a rolling 30-day period: each user is counted only once within this period, and the license seat is automatically released if no connection has been recorded for more than one month. In addition, a new version of the WALLIX Bastion License page has been introduced and redesigned to improve readability and license consumption tracking for both SaaS and On-Premise solutions. It enables real-time monitoring of key indicators such as the number of "Named Users", "Concurrent Users", accessed "Resources", and the usage of paid options.
Improve access to web applications through Web Session Manager to provide a smoother, more secure experience and better compatibility with a wider range of applications. New configurable parameters are now available for each web application to improve compatibility and simplify user access, notably through automatic credential injection. In addition, improve the Web Session Manager installation process to facilitate deployment and reduce friction for administration teams.
Add enhanced visibility on Web Session Manager usage on the WALLIX Bastion License page, with tracking for both Named users and Concurrent users, enabling more accurate monitoring and optimization of license consumption.
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
Improve authentication on RDP and VNC servers by allowing the use of trusted X.509 Certificate Authorities (CA), simplifying configuration when server certificates rotate frequently.
The following features and improvements have been implemented in this version:
No improvement was part of this version.
Following the removal of the DRBD-based High Availability feature in Bastion 12, the eth1 network interface can now be configured and used like any other regular network interface.
No improvement was part of this version.
WALLIX Bastion now supports Kerberos authentication on RDP Proxy primary connection. This provides single sign-on for Active Directory users.
The following features and improvements have been implemented in this version:
Improve the Target groups configuration in WALLIX Bastion. It has been redesigned with a simplified, modern interface. Group configuration is now faster and more intuitive: targets can be added in just a few clicks, deletions are easier, and all actions are performed from a single, unified page.
Improve session history in WALLIX Bastion. The new interface provides clearer and smoother monitoring of activities performed within a session. This redesign makes it easier to identify critical behaviors and delivers a more streamlined user experience.
Increase the password history for WALLIX Bastion and Access Manager local accounts from 15 to 50, preventing reuse of old passwords and enhancing account security.
WALLIX Bastion now offers enhanced Web target administration and analysis, giving teams greater control and visibility. Web session activity can be exported in CSV format, making audits and analysis faster and more efficient. A new notification capability provides real-time monitoring of access to critical Web applications, strengthening security and operational responsiveness. Web access also supports account mapping through transformation rules, expanding authentication options and offering more flexibility in access management.
Web sessions managed with Web Session Manager now include advanced auditing capabilities. These capabilities include session video playback and metadata downloads, which improve traceability, compliance, and analysis of risky behaviors. Web session logs can also be forwarded to SIEM tools, enabling centralized visibility and enhanced incident detection.
The analysis of large files in WALLIX Bastion is now optimized for all sessions supporting file transfers. A new parameter allows configuring the analysis timeout for ICAP server responses, ensuring reliable, complete, and secure transfers even for very large files.
Deprecate the kerberos-password method in favor of the standard kerberos method for Kerberos authentication.
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
No improvement was part of this version.
The following features and improvements have been implemented in this version:
The new WALLIX Web Session Manager solution provides secure access to web applications using remote browser isolation technology. Users can seamlessly access web targets directly from their browser via WALLIX Bastion, without needing plugins or add-ons. Credential can be injected securely to prevent user accessing them. This new native component integrates seamlessly into the WALLIX Bastion ecosystem. Additionally, administrators can control each session by preventing unauthorized redirections or allowing them and managing common behaviors within a user's web session, such as copy/paste, file upload/download, etc.
To enhance security and simplify access management, API keys can now be linked to profiles. Default profiles have been introduced to ensure a standardized, reliable configuration tailored to each ecosystem with Access Manager (compatibility starting from version WALLIX Access Manager 5.2).
When upgrading to this version, all existing API keys are automatically updated to use the product_administrator profile.
WALLIX Bastion and WALLIX Access Manager now support integration with identity providers using the OpenID Connect (OIDC) standard. This enhancement facilitates centralized user management across the entire ecosystem, streamlining deployment within existing infrastructures. With OIDC, users can enjoy Single Sign-On (SSO), making access more seamless and efficient.
The new WAMUT client is now available for managing Universal Tunneling sessions on your workstation. It features a graphical interface that enhances visibility into the current session state. Additionally, the user workflow is now unified across both WALLIX Bastion and WALLIX Access Manager.
The Seamless Connection feature offers a new mode, which no longer requires admin rights on the user workstation. Users still enjoy the same seamless experience, making Universal Tunneling easy to adopt. This new mode also enhances user experience with fat clients using a static port on the user workstation (like TIA Portal, SoMachine, etc.). To enable the workflow for WALLIX Access Manager users, both WALLIX Bastion and WALLIX Access Manager must be upgraded to versions 12.2 and 5.2, respectively.
A new authentication for SSH proxy users based on FIDO2 hardware is available. Transfer with agent forwarding (SSH proxy to target) is also supported, if the client used supports it.
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
API keys can be linked to a non-editable profile, restricting the rights of users logging in with an API key. New default non-editable profiles have been introduced to simplify API key configuration with Access Manager (compatibility starting from version 5.2).
Bastion supports OpenID Connect, enabling seamless authentication with identity providers supporting the standard. This integration enhances security and simplifies user access management. Administrators benefit from streamlined identity federation and improved access control. With Single Sign-On (SSO), users can access Bastion without repeatedly entering credentials.
The RDP session resolution can be enforced by the administrator through the RDP connection policy. This new option facilitates connections to servers and systems that support only a specific resolution, preventing display issues or session crashes.
In network and AD discovery, latency is now measured for each discovered devices and available in the scan job results.
The following features and improvements have been implemented in this version:
Bastion 12 introduces a new system upgrade procedure. As a result, if you have a WALLIX Bastion prior to version 12 and wish to upgrade to Bastion 12, refer to chapter 6 of the Deployment Guide.
Bastion 12 introduces a new minor upgrade process to enhance efficiency and user experience. The new process relies on the wabupgrade account making it easier to upgrade from version 12 to version 12.X. Refer to the Deployment Guide, chapter 7 for detailed instructions.
Bastion 12.0.1 introduces a new default behavior for the “Enable Kerberos” option, enabling it by default which means that NLA Kerberos is now the first attempted authentication method. However, when restoring the backup of a Bastion anterior to 12.0.1, the configuration of authentication mechanisms is not modified. That means that values set for NLA and Kerberos are restored as defined in that backup file. For example, if Enable Kerberos option was disabled, this option remains disabled after the restoration, even if the option is now enabled by default.
Bastion 12.0.1 also introduces new options for RDP target connections. To ensure that the target cannot negotiate an authentication protocol lower than that specified by the connection policy, fallback mechanisms are disabled by default. However, for greater granularity, you can modify fallback mechanisms for connections to RDP targets. The options are:
We strongly encourage you to review your connection policies and make any necessary updates to the fallback mechanism to better suit your needs.
WALLIX follows the Microsoft recommendation to use the domain account for RDP sessions. As a result, WALLIX recommends to use NLA Kerberos authentication when using target account in Active Directory. That means the “Allow NLA NTLM fallback”, “Allow TLS only fallback”, and “Allow RDP legacy fallback” options must be disabled.
When using a local account on a target, Microsoft and WALLIX recommend:
For earlier targets (windows 2003 and older), you must enable the “Allow RDP legacy fallback” option.
The following features and improvements have been implemented in this version:
This version includes all fixes implemented from WALLIX Bastion 12.0 and listed in the sections below.
Fix additional user certificate checks. Certificates with a NUL in the key ID, force-command or source-address, duplicate critical options, or malformed option data are now also rejected. * WAB-21162: Fix SSH proxy authentication with FIDO security keys (sk-ecdsa and sk-ed25519), which did not require user presence. These keys must now report user presence (a physical touch), as with OpenSSH. Keys generated with the “-O no-touch-required” option can no longer authenticate, unless they are used with a certificate carrying the no-touch-required extension. * WAB-21163: Fix the SSH proxy, which accepted authentication methods disabled in its configuration when a client requested them. The SSH proxy now also disconnects a client that changes its username during authentication. * WAB-21210: Fix memory corruption when the RDP proxy processes client connection and logon data before authentication. Clients sending more than one network data block at connection are disconnected. * WAB-21211: Fix text conversion, graphics caches, Kerberos credential cache handling and file reads in the RDP proxy. Kerberos authentication to targets requires mutual authentication and confidentiality before credentials are sent. * WAB-21213: Fix issues in the headless client and development and test tools. * WAB-21214: Fix processing of recordings, signatures and configuration values. Command markers such as ${PASSWORD} in application names, accounts and Session Probe arguments are substituted in one pass. With persist_bitmap_cache_on_disk enabled, the persistent bitmap cache is rebuilt for host names containing / or %. * WAB-21215: Fix RDP client capability checks before authentication, including glyph cache sizes. Malformed capabilities from a client or target end the session. * WAB-21217: Fix length checks on RemoteApp program names and arguments forwarded to the target. Overlong fields are truncated. * WAB-21218: Fix processing of glyph (text drawing) orders from RDP targets. Malformed glyph orders are dropped or end the session. * WAB-21219: Fix decompression of RDP data from the target. Corrupted compressed data ends the session. * WAB-21220: Fix RemoteFX graphics decoding in the RDP proxy. Invalid or oversized surfaces and tiles from the target are dropped or end the session. * WAB-21221: Fix rendering of target graphics orders during session recording and OCR. Drawing is clipped to the session screen. * WAB-21222: Fix processing of palette and bitmap updates from RDP targets. Malformed palette updates and bitmaps wider than 65,532 pixels end the session. * WAB-21223: Fix length checks on drawing orders, updates and capabilities from RDP targets. Truncated or inconsistent data ends the session. * WAB-21224: Fix server redirection requests from RDP targets. Overlong redirection fields are truncated. * WAB-21225: Fix TLS failure handling for RDP target connections. A failed TLS handshake or a certificate rejected by the [server_cert] policy ends the connection instead of continuing unencrypted. * WAB-21226: Fix Standard RDP Security checks on client data when [client] tls_fallback_legacy is enabled. Unencrypted data or data with an invalid integrity check ends the session. * WAB-21227: Fix enforcement of drive redirection read and write permissions. Without write permission, the target cannot create, modify, rename or delete files or change their attributes. Applications opening files for writing on a read-only redirected drive may receive access-denied errors. * WAB-21228: Fix virtual channel filtering and clipboard antivirus/DLP checks. Virtual channel data marked as compressed ends the session; clipboard file data beyond the announced size is refused. * WAB-21229: Fix file access confinement on proxy-managed drives, including the Session Probe launcher drive. Target requests outside the drive or using another drive's file handle are refused. * WAB-21230: Fix length checks on clipboard and drive redirection data. Malformed messages from a client or target are refused or end the session. * WAB-21231: Fix ZRLE decoding and file transfer error handling for VNC targets. Invalid ZRLE data from the target ends the session. * WAB-21232: Fix resource limits on desktop sizes, bitmaps, drive redirection and Session Probe file reads requested by RDP targets. Desktops exceeding 32,766 pixels per dimension or 67,108,864 pixels in total area (8,192 x 8,192) end the session, including multi-monitor layouts. * WAB-21233: Fix memory use for client device announcements and messages on very narrow screens. Devices announced with more than 1 MiB of data are not redirected, and a warning is logged. * WAB-21234: Fix file transfer auditing for drive redirection and clipboard. Transfers on drives removed during the session are audited, and clipboard file names and sizes are logged correctly. * WAB-21235: Fix RDP proxy logging of session secrets and user file names. The auto-reconnect cookie is no longer logged, drive directory listings require drive redirection debug verbosity, and CredSSP/NLA debug traces show only credential lengths. * WAB-21236: Fix reading and verification of altered session recordings. The “redver” tool rejects recordings without a checksum, including archived version 1 recordings, unless the “--allow-nochecksum” option is specified. * WAB-21237: Fix the “wallixcelery” service running out of memory after unlocking the encryption key, on Bastions with limited memory and many accounts. This prevented the automatic check-in of expired checkouts. * WAB-21244: Fix memory corruption during SSH proxy user authentication with Kerberos (GSSAPI). Malformed or repeated GSSAPI authentication messages are now refused. * WAB-21245: Fix numeric option parsing and agent request forwarding in the SSH proxy. Malformed or out-of-range numeric values are refused instead of truncated. * WAB-21247: Fix resource leaks and error handling in SSH proxy Kerberos (GSSAPI) authentication. Kerberos tokens are no longer written to packet-level logs. * WAB-21248: Fix key exchange message and value validation and failure handling in the SSH proxy. Peers are disconnected if they send malformed or out-of-range key exchange values or keep the same keys for 2^32 packets. * WAB-21249: Fix credential and key cleanup in the SSH proxy. Target passwords, X11 cookies, private key material and session keys are now wiped from memory after use. * WAB-21250: Fix SSH proxy restriction patterns with inline flags or verbose-mode comments, SFTP sessions using protocol versions other than 3, and IPv6 UDP recording. These patterns now apply correctly, the requested SFTP version is capped at 3, and IPv6 UDP flows are recorded. * WAB-21251: Fix validation of received packets, version banners and protocol fields in the SSH proxy. Malformed SSH packet layouts now end the connection, and client version lines up to 255 bytes are accepted. * WAB-21252: Fix SSH proxy signature algorithm checks and authentication method selection for targets. Public key signatures must use the requested algorithm, and method names must match in full. SHA-2 signatures for ssh-rsa certificates and clients based on OpenSSH 7.0 to 7.7 remain accepted. * WAB-21253: Fix memory corruption when an SSH target sends an invalid host key signature during key exchange. The SSH proxy now fails the connection cleanly. * WAB-21254: Fix SSH proxy host key verification, which accepted a new key type from a known target. Targets that no longer offer their stored host key type are now refused; the error names the received and stored key types. * WAB-21255: Fix memory corruption in the terminal emulator used by the SSH proxy for real-time session display and transcripts. Combining characters, wide characters and terminal resizes now render correctly in transcripts. * WAB-21256: Fix SSH proxy command restriction and file transfer analysis handling. Analysis errors now close the channel, and restriction patterns apply to lines with invalid UTF-8. Data matching a warning pattern is discarded in full, and data accepted by the target in several parts is recorded once. * WAB-21258: Fix unbounded memory and CPU use in SSH proxy channel handling and Telnet option negotiation. Peers sending data well past the granted window are disconnected. * WAB-21259: Fix SSH proxy log injection through client or target text, including banners and disconnect messages. Control characters and invalid UTF-8 in this text are now escaped in logs and error messages. * WAB-21336: Update the MariaDB package to fix the following security issues: CVE-2026-47023, CVE-2026-60184, CVE-2026-60331, CVE-2026-60585, CVE-2026-60747, CVE-2026-61081. * WAB-21337: Update the linux package to fix the following security issues: CVE-2023-52629, CVE-2023-52676, CVE-2023-53231, CVE-2023-53336, CVE-2023-53353, CVE-2023-53429, CVE-2023-53491, CVE-2023-53538, CVE-2023-53574, CVE-2023-53627, CVE-2023-53762, CVE-2023-53851, CVE-2023-53857, CVE-2023-53999, CVE-2023-54227, CVE-2023-54233, CVE-2024-35887, CVE-2024-49568, CVE-2024-50017, CVE-2024-50029, CVE-2024-58097, CVE-2025-21649, CVE-2025-21651, CVE-2025-21759, CVE-2025-22039, CVE-2025-22103, CVE-2025-23129, CVE-2025-37833, CVE-2025-40074, CVE-2025-40097, CVE-2025-68190, CVE-2025-68736, CVE-2026-23191, CVE-2026-23447, CVE-2026-23448, CVE-2026-31420, CVE-2026-43088, CVE-2026-43198, CVE-2026-43288, CVE-2026-45897, CVE-2026-46090, CVE-2026-52944, CVE-2026-52988, CVE-2026-53005, CVE-2026-53078, CVE-2026-64210, CVE-2026-68097, CVE-2026-68161, CVE-2026-68236, CVE-2026-68286, CVE-2026-68287, CVE-2026-68288, CVE-2026-68289, CVE-2026-68391, CVE-2026-72334, CVE-2026-72402, CVE-2026-72413, CVE-2026-74268, CVE-2026-74289, CVE-2026-74294, CVE-2026-74334, CVE-2026-74474, CVE-2026-74496, CVE-2026-74521, CVE-2026-74565, CVE-2026-80521, CVE-2026-80671, CVE-2026-80689, CVE-2026-80833, CVE-2026-80834, CVE-2026-80912, CVE-2026-80914, CVE-2026-80928, CVE-2026-80930, CVE-2026-80931, CVE-2026-80932, CVE-2026-80938, CVE-2026-80941, CVE-2026-80944, CVE-2026-80949, CVE-2026-80951, CVE-2026-80952, CVE-2026-80963, CVE-2026-80964, CVE-2026-80965, CVE-2026-80966, CVE-2026-80967, CVE-2026-80968, CVE-2026-80969, CVE-2026-80971, CVE-2026-80972, CVE-2026-80973, CVE-2026-80976, CVE-2026-80977, CVE-2026-80978, CVE-2026-80982, CVE-2026-80983, CVE-2026-80987, CVE-2026-80988, CVE-2026-80992, CVE-2026-80994, CVE-2026-81000, CVE-2026-81001, CVE-2026-81002, CVE-2026-81003, CVE-2026-81005, CVE-2026-81007, CVE-2026-81008, CVE-2026-81017, CVE-2026-89440, CVE-2026-89444, CVE-2026-89456, CVE-2026-89457, CVE-2026-89458, CVE-2026-89461, CVE-2026-89463, CVE-2026-89464, CVE-2026-89469, CVE-2026-89470, CVE-2026-89471, CVE-2026-89474, CVE-2026-89475, CVE-2026-89476, CVE-2026-89477, CVE-2026-89478, CVE-2026-89479, CVE-2026-89480, CVE-2026-89481, CVE-2026-89482, CVE-2026-89483, CVE-2026-89485, CVE-2026-89487, CVE-2026-89488, CVE-2026-89489, CVE-2026-89490, CVE-2026-89491, CVE-2026-89493, CVE-2026-89494, CVE-2026-89495, CVE-2026-89496, CVE-2026-89497, CVE-2026-89498, CVE-2026-89504, CVE-2026-89508, CVE-2026-89510, CVE-2026-89511, CVE-2026-89512, CVE-2026-89515, CVE-2026-89524, CVE-2026-89525, CVE-2026-89532, CVE-2026-89533, CVE-2026-89538, CVE-2026-89540, CVE-2026-89541, CVE-2026-89542, CVE-2026-89548, CVE-2026-89549, CVE-2026-89551, CVE-2026-89554, CVE-2026-89555, CVE-2026-89557, CVE-2026-89559, CVE-2026-89560, CVE-2026-89562, CVE-2026-89563, CVE-2026-89565, CVE-2026-89569, CVE-2026-89573, CVE-2026-89575, CVE-2026-89576, CVE-2026-89579, CVE-2026-89582, CVE-2026-89583, CVE-2026-89585, CVE-2026-89586, CVE-2026-89587, CVE-2026-89594, CVE-2026-89595, CVE-2026-89596, CVE-2026-89597, CVE-2026-89599, CVE-2026-89604, CVE-2026-89605, CVE-2026-89606, CVE-2026-89607, CVE-2026-89608, CVE-2026-89609, CVE-2026-89615, CVE-2026-89616, CVE-2026-89617, CVE-2026-89621, CVE-2026-89626, CVE-2026-89627, CVE-2026-89628, CVE-2026-89634, CVE-2026-89636, CVE-2026-89640, CVE-2026-89643, CVE-2026-89649, CVE-2026-89650, CVE-2026-89653, CVE-2026-89655, CVE-2026-89656, CVE-2026-89662, CVE-2026-89663, CVE-2026-89665, CVE-2026-89669, CVE-2026-89674, CVE-2026-89684, CVE-2026-89694, CVE-2026-89696, CVE-2026-89697, CVE-2026-89699, CVE-2026-89704, CVE-2026-89706, CVE-2026-89710, CVE-2026-89711, CVE-2026-89712, CVE-2026-89720, CVE-2026-89723, CVE-2026-89724, CVE-2026-89725, CVE-2026-89726, CVE-2026-89729, CVE-2026-89730, CVE-2026-89732, CVE-2026-89733, CVE-2026-89736, CVE-2026-89741, CVE-2026-89742, CVE-2026-89744, CVE-2026-89746, CVE-2026-89749, CVE-2026-89751, CVE-2026-89752, CVE-2026-89753, CVE-2026-89756, CVE-2026-89765, CVE-2026-89776, CVE-2026-89777, CVE-2026-89778, CVE-2026-89779, CVE-2026-89780, CVE-2026-89781, CVE-2026-89782, CVE-2026-89783, CVE-2026-89784, CVE-2026-89785, CVE-2026-89786, CVE-2026-89787, CVE-2026-89789, CVE-2026-89792, CVE-2026-89796, CVE-2026-89816, CVE-2026-89817, CVE-2026-89818, CVE-2026-89821, CVE-2026-89822, CVE-2026-89823, CVE-2026-89824, CVE-2026-89843, CVE-2026-89845, CVE-2026-89846, CVE-2026-89847, CVE-2026-89849, CVE-2026-89850, CVE-2026-89851, CVE-2026-89852, CVE-2026-89853, CVE-2026-89854, CVE-2026-89855, CVE-2026-89856, CVE-2026-89858, CVE-2026-89861, CVE-2026-89863, CVE-2026-89864, CVE-2026-89865, CVE-2026-89870, CVE-2026-89871, CVE-2026-89872, CVE-2026-89876, CVE-2026-89877, CVE-2026-89878, CVE-2026-89879, CVE-2026-89880, CVE-2026-89881, CVE-2026-89883, CVE-2026-89887, CVE-2026-89888, CVE-2026-89890, CVE-2026-89891, CVE-2026-89892, CVE-2026-89893, CVE-2026-89894, CVE-2026-89895, CVE-2026-89896, CVE-2026-89897, CVE-2026-89901, CVE-2026-89922, CVE-2026-89923, CVE-2026-89924, CVE-2026-89925, CVE-2026-89926, CVE-2026-89927, CVE-2026-89930, CVE-2026-89932, CVE-2026-89936, CVE-2026-89937, CVE-2026-89939, CVE-2026-89945, CVE-2026-89946, CVE-2026-89947, CVE-2026-89948, CVE-2026-89949, CVE-2026-89951, CVE-2026-89952, CVE-2026-89953, CVE-2026-89954, CVE-2026-89957, CVE-2026-89959, CVE-2026-89964, CVE-2026-89965, CVE-2026-89968, CVE-2026-89969, CVE-2026-89970, CVE-2026-89973, CVE-2026-89979, CVE-2026-89980, CVE-2026-89982, CVE-2026-89983, CVE-2026-89984, CVE-2026-89988, CVE-2026-89989, CVE-2026-89992, CVE-2026-89993, CVE-2026-89997, CVE-2026-89998, CVE-2026-89999, CVE-2026-90000, CVE-2026-90003, CVE-2026-90007, CVE-2026-90011, CVE-2026-90015, CVE-2026-90017, CVE-2026-90018, CVE-2026-90019, CVE-2026-90020, CVE-2026-90025, CVE-2026-90031, CVE-2026-90032, CVE-2026-90033, CVE-2026-90034, CVE-2026-90049, CVE-2026-90053, CVE-2026-90054, CVE-2026-90055, CVE-2026-90056, CVE-2026-90057, CVE-2026-90058, CVE-2026-90060, CVE-2026-90062, CVE-2026-90063, CVE-2026-90067, CVE-2026-90068, CVE-2026-90070, CVE-2026-90071, CVE-2026-90072, CVE-2026-90073, CVE-2026-90074, CVE-2026-90075, CVE-2026-90078, CVE-2026-90081, CVE-2026-90088, CVE-2026-90090, CVE-2026-90091, CVE-2026-90092, CVE-2026-90102, CVE-2026-90103, CVE-2026-90107, CVE-2026-90108, CVE-2026-90110, CVE-2026-90114, CVE-2026-90122, CVE-2026-90124, CVE-2026-90126, CVE-2026-90128, CVE-2026-90140, CVE-2026-90141, CVE-2026-90143, CVE-2026-90151, CVE-2026-90157, CVE-2026-90160, CVE-2026-90176, CVE-2026-90180, CVE-2026-90184, CVE-2026-90185, CVE-2026-90186, CVE-2026-90188, CVE-2026-90189, CVE-2026-90190, CVE-2026-90194, CVE-2026-90196, CVE-2026-90198, CVE-2026-90202, CVE-2026-90203, CVE-2026-90207, CVE-2026-90209, CVE-2026-90214, CVE-2026-90216, CVE-2026-90218, CVE-2026-90219, CVE-2026-90221, CVE-2026-90222, CVE-2026-90223, CVE-2026-90224, CVE-2026-90225, CVE-2026-90226, CVE-2026-90228, CVE-2026-90245, CVE-2026-90248, CVE-2026-90249, CVE-2026-90251, CVE-2026-90253, CVE-2026-90254, CVE-2026-90255, CVE-2026-90257, CVE-2026-90274, CVE-2026-90281, CVE-2026-90283, CVE-2026-90284, CVE-2026-90285, CVE-2026-90286, CVE-2026-90287, CVE-2026-90290, CVE-2026-90292, CVE-2026-90293, CVE-2026-90294, CVE-2026-90295, CVE-2026-90296, CVE-2026-90297, CVE-2026-90298, CVE-2026-90302, CVE-2026-90303, CVE-2026-90307, CVE-2026-90309, CVE-2026-90314, CVE-2026-90316, CVE-2026-90318, CVE-2026-90319, CVE-2026-90327, CVE-2026-90329, CVE-2026-90334, CVE-2026-90341, CVE-2026-90348, CVE-2026-90352, CVE-2026-90353, CVE-2026-90354, CVE-2026-90357, CVE-2026-90360, CVE-2026-90361, CVE-2026-90362, CVE-2026-90372, CVE-2026-90378, CVE-2026-90382, CVE-2026-90386, CVE-2026-90388, CVE-2026-90391, CVE-2026-90393, CVE-2026-90394, CVE-2026-90395, CVE-2026-90403, CVE-2026-90411, CVE-2026-90413, CVE-2026-90414, CVE-2026-90415, CVE-2026-90416, CVE-2026-90419, CVE-2026-90420, CVE-2026-90431, CVE-2026-90434, CVE-2026-90435, CVE-2026-92476, CVE-2026-92477, CVE-2026-92481, CVE-2026-92494, CVE-2026-92496, CVE-2026-92498, CVE-2026-92501, CVE-2026-92504, CVE-2026-92507, CVE-2026-92508, CVE-2026-92509, CVE-2026-92510, CVE-2026-92511, CVE-2026-92512, CVE-2026-92514, CVE-2026-92521, CVE-2026-92522, CVE-2026-92523, CVE-2026-92524, CVE-2026-92525, CVE-2026-93037, CVE-2026-93039, CVE-2026-93040, CVE-2026-93041, CVE-2026-93046, CVE-2026-93048, CVE-2026-93049, CVE-2026-93050, CVE-2026-93051, CVE-2026-93052, CVE-2026-93053, CVE-2026-93054, CVE-2026-93055, CVE-2026-93056, CVE-2026-93061, CVE-2026-93063, CVE-2026-93064, CVE-2026-93067, CVE-2026-93073, CVE-2026-93095, CVE-2026-93098, CVE-2026-93102, CVE-2026-93103, CVE-2026-93108, CVE-2026-93109, CVE-2026-93110, CVE-2026-93114, CVE-2026-93115, CVE-2026-93117, CVE-2026-93118, CVE-2026-93120, CVE-2026-93130, CVE-2026-93131, CVE-2026-93136, CVE-2026-93137, CVE-2026-93138, CVE-2026-93140, CVE-2026-93141, CVE-2026-93142, CVE-2026-93145, CVE-2026-93149, CVE-2026-93151, CVE-2026-93152, CVE-2026-93158, CVE-2026-93159, CVE-2026-93160, CVE-2026-93161, CVE-2026-93165, CVE-2026-93167, CVE-2026-93170, CVE-2026-93177, CVE-2026-93178, CVE-2026-93182, CVE-2026-93183, CVE-2026-93185, CVE-2026-93188, CVE-2026-93189, CVE-2026-93190, CVE-2026-93191, CVE-2026-93203, CVE-2026-93204, CVE-2026-93206, CVE-2026-93210, CVE-2026-93213, CVE-2026-93214, CVE-2026-93219, CVE-2026-93222, CVE-2026-93226, CVE-2026-93234, CVE-2026-93236, CVE-2026-93242, CVE-2026-93245, CVE-2026-93247, CVE-2026-93252, CVE-2026-93256, CVE-2026-93261, CVE-2026-93262, CVE-2026-93264, CVE-2026-93268, CVE-2026-93271, CVE-2026-93274, CVE-2026-93278, CVE-2026-93279, CVE-2026-93280, CVE-2026-93281, CVE-2026-93283, CVE-2026-93286, CVE-2026-93287, CVE-2026-93288, CVE-2026-93781, CVE-2026-93782, CVE-2026-93783, CVE-2026-93784, CVE-2026-93785, CVE-2026-93787, CVE-2026-93788, CVE-2026-93789, CVE-2026-93795, CVE-2026-93797, CVE-2026-93798, CVE-2026-93800, CVE-2026-93802, CVE-2026-93803, CVE-2026-93805, CVE-2026-93806, CVE-2026-93807, CVE-2026-93808, CVE-2026-93810, CVE-2026-93811, CVE-2026-93812, CVE-2026-93813, CVE-2026-93814, CVE-2026-93815, CVE-2026-93816, CVE-2026-93819, CVE-2026-93820, CVE-2026-93821, CVE-2026-93822, CVE-2026-93824, CVE-2026-93825, CVE-2026-93826, CVE-2026-93830, CVE-2026-97407, CVE-2026-97408, CVE-2026-97411, CVE-2026-97413, CVE-2026-97415, CVE-2026-97416, CVE-2026-97417, CVE-2026-97418, CVE-2026-97419, CVE-2026-97420, CVE-2026-97421, CVE-2026-97427, CVE-2026-97430, CVE-2026-97434, CVE-2026-97435, CVE-2026-97436, CVE-2026-97437, CVE-2026-97438, CVE-2026-97439, CVE-2026-97440, CVE-2026-97441, CVE-2026-97442, CVE-2026-97444, CVE-2026-97445, CVE-2026-97446, CVE-2026-97448, CVE-2026-97449, CVE-2026-97450, CVE-2026-97451, CVE-2026-97452, CVE-2026-97453, CVE-2026-97454, CVE-2026-97455, CVE-2026-97456, CVE-2026-97472, CVE-2026-97475, CVE-2026-97476, CVE-2026-97481, CVE-2026-97482, CVE-2026-97483, CVE-2026-97484, CVE-2026-97485, CVE-2026-97486, CVE-2026-97487, CVE-2026-97488, CVE-2026-97489, CVE-2026-97490, CVE-2026-97491, CVE-2026-97492, CVE-2026-97495, CVE-2026-97497, CVE-2026-97502, CVE-2026-97506, CVE-2026-97507, CVE-2026-97508, CVE-2026-97509, CVE-2026-97510, CVE-2026-97516, CVE-2026-97517, CVE-2026-97523, CVE-2026-97524, CVE-2026-97539, CVE-2026-97540, CVE-2026-97541, CVE-2026-97556, CVE-2026-97557, CVE-2026-97564, CVE-2026-97568, CVE-2026-97572, CVE-2026-97573, CVE-2026-97576, CVE-2026-97581, CVE-2026-97582, CVE-2026-97592, CVE-2026-97596, CVE-2026-97598, CVE-2026-97601, CVE-2026-97604, CVE-2026-97608, CVE-2026-97611, CVE-2026-97612, CVE-2026-97899, CVE-2026-97904, CVE-2026-97905, CVE-2026-97909, CVE-2026-97910, CVE-2026-97920, CVE-2026-97921, CVE-2026-97922, CVE-2026-97923, CVE-2026-97925, CVE-2026-97926, CVE-2026-97927, CVE-2026-97930, CVE-2026-97931, CVE-2026-97940, CVE-2026-97948, CVE-2026-97951, CVE-2026-97952, CVE-2026-97954, CVE-2026-97957, CVE-2026-97958, CVE-2026-97959, CVE-2026-97963, CVE-2026-97964, CVE-2026-97969, CVE-2026-97970, CVE-2026-97973, CVE-2026-97977, CVE-2026-97979, CVE-2026-97981, CVE-2026-97982, CVE-2026-97986, CVE-2026-97987, CVE-2026-97991, CVE-2026-97993, CVE-2026-97995, CVE-2026-97998, CVE-2026-98006, CVE-2026-98008, CVE-2026-98009, CVE-2026-98010, CVE-2026-98011, CVE-2026-98012, CVE-2026-98013, CVE-2026-98014, CVE-2026-98015, CVE-2026-98016, CVE-2026-98017, CVE-2026-98022, CVE-2026-98023, CVE-2026-98025, CVE-2026-98027, CVE-2026-98030, CVE-2026-98031, CVE-2026-98046, CVE-2026-98055, CVE-2026-98063, CVE-2026-98064, CVE-2026-98066, CVE-2026-98068, CVE-2026-98069, CVE-2026-98070, CVE-2026-98071, CVE-2026-98072, CVE-2026-98074, CVE-2026-98075, CVE-2026-98076, CVE-2026-98077, CVE-2026-98078, CVE-2026-98080, CVE-2026-98088, CVE-2026-98089, CVE-2026-98090, CVE-2026-98091, CVE-2026-98092, CVE-2026-98094, CVE-2026-98095, CVE-2026-98096, CVE-2026-98098, CVE-2026-98104, CVE-2026-98108, CVE-2026-98113, CVE-2026-98116, CVE-2026-98121, CVE-2026-98123, CVE-2026-98128, CVE-2026-98129, CVE-2026-98130, CVE-2026-98154, CVE-2026-98157, CVE-2026-98158, CVE-2026-98159, CVE-2026-98160, CVE-2026-98167, CVE-2026-98169, CVE-2026-98171, CVE-2026-98172, CVE-2026-98181, CVE-2026-98185, CVE-2026-98186, CVE-2026-98187, CVE-2026-98188, CVE-2026-98189, CVE-2026-98190, CVE-2026-98191, CVE-2026-98194, CVE-2026-98195, CVE-2026-98196, CVE-2026-98197, CVE-2026-98199, CVE-2026-98201, CVE-2026-98202, CVE-2026-98203, CVE-2026-98204, CVE-2026-98205, CVE-2026-98207, CVE-2026-98208, CVE-2026-98209, CVE-2026-98210, CVE-2026-98213, CVE-2026-98217, CVE-2026-98221, CVE-2026-98227, CVE-2026-98233, CVE-2026-98234, CVE-2026-98236, CVE-2026-98237, CVE-2026-98238, CVE-2026-98239, CVE-2026-98241, CVE-2026-98246, CVE-2026-98247, CVE-2026-98249, CVE-2026-98251, CVE-2026-98252, CVE-2026-98253, CVE-2026-98255, CVE-2026-98257, CVE-2026-98260, CVE-2026-98262, CVE-2026-98264, CVE-2026-98272, CVE-2026-98275, CVE-2026-98276, CVE-2026-98282, CVE-2026-98283, CVE-2026-98287, CVE-2026-98290, CVE-2026-98298, CVE-2026-98299, CVE-2026-98300, CVE-2026-98301, CVE-2026-98302, CVE-2026-98303, CVE-2026-98306, CVE-2026-98308, CVE-2026-98311, CVE-2026-98312, CVE-2026-98314, CVE-2026-98319, CVE-2026-98320, CVE-2026-98322, CVE-2026-98323, CVE-2026-98325, CVE-2026-98326, CVE-2026-98328, CVE-2026-98331, CVE-2026-98339, CVE-2026-98340, CVE-2026-98342, CVE-2026-98343, CVE-2026-98344, CVE-2026-98345, CVE-2026-98347, CVE-2026-98348, CVE-2026-98349, CVE-2026-98351, CVE-2026-98352, CVE-2026-98354, CVE-2026-98357, CVE-2026-98358, CVE-2026-98359, CVE-2026-98360, CVE-2026-98362, CVE-2026-98363, CVE-2026-98367, CVE-2026-98368, CVE-2026-98369, CVE-2026-98370, CVE-2026-98374, CVE-2026-98378, CVE-2026-98379, CVE-2026-98380, CVE-2026-98381, CVE-2026-98383, CVE-2026-98388, CVE-2026-98398, CVE-2026-98402, CVE-2026-98404, CVE-2026-98406, CVE-2026-98407, CVE-2026-98410, CVE-2026-98413, CVE-2026-98416, CVE-2026-98417, CVE-2026-98419, CVE-2026-98421, CVE-2026-98422, CVE-2026-98423, CVE-2026-98426, CVE-2026-98428, CVE-2026-98429, CVE-2026-98430, CVE-2026-98432, CVE-2026-99999, CVE-2026-100070, CVE-2026-100071, CVE-2026-100075, CVE-2026-100078. * WAB-21343: Fix the Windows password change over WinRM: a single quote or a typographic quote in the login or the new password of an account is now escaped and no longer interpreted as PowerShell code. * WAB-21358: Update the python-django package to fix the following security issues: CVE-2026-77050, CVE-2026-87975. * WAB-21379: Update the libssh package to fix the following security issues: CVE-2026-0964, CVE-2026-0965, CVE-2026-0966, CVE-2026-0967, CVE-2026-0968, CVE-2026-3731, CVE-2026-59843, CVE-2026-59844, CVE-2026-59845, CVE-2026-59846, CVE-2026-59847, CVE-2026-59848, CVE-2026-59850. * WAB-21380: Update the ca-certificates package to fix the security issues reported in the Debian advisory DLA-4845-1.