Monthly Release Notes - February 2026

Jump to:

 

Agari


Suspicious Email Analysis

Version 2026.02

February 2026

New Feature
  • This release incorporates the latest Fortra email security ML and AI detection models into the SEA analysis pipeline.

Enhancements
  • New Malicious Sub-Classification "Response-Recon"

    • This classification identifies early-stage attacker tactics focused on reconnaissance, where the attacker's primary objective is gathering information, not immediately compromising systems or stealing credentials.

  • Classification Change fields added for Incidents

    • The new fields will track the original classification of an incident if it changes, along with the time of the change and the type of change made (for example, whether it was a false positive or false negative). This data can be accessed via the Incident Data API.

  • Web App Incident Download

    • The maximum number of rows for Incident CSV downloads has increased from 10,000 to 30,000.

Fixes
  • Update on email header parsing

    • Special characters will now be retained in the Message ID field.

  • Various bug fixes and updates.

Back to Top

 

Boldon James


Email and Office Classifier

Version 3.22.1

February 26, 2026

Fixes
  • When changing the label or saving a Microsoft Word document that has narrow margins, the document footers will no longer appear unless a visual marking is applied to that footer.
  • In Email Classifier, the feature to classify unlabeled attachments will no longer trigger an inconsistent markings error.

Exchange Classifier

Version 3.2.1

February 4, 2026

New Features
  • Added support for Exchange Server Subscription Edition (SE).
  • The same installer now supports installation on Exchange Server 2019 and Exchange Server SE.
Enhancements
  • Confirmed support for Windows Server 2025.
Security Updates
  • Updated to latest dependencies to address identified vulnerabilities.

Back to Top

 

CCSS


QMessage Monitor

Version 9.02

February 5, 2026

Fixes
  • Fixed issue where under certain conditions a minor issue in the timing calculations could affect QMM Events.

  • Fixed issue where under certain conditions a program attached to an Automatic Response, would issue an MCH3601 error message.

  • Fixed issue where the Maintenance client failed when a user tried to save an automated response that had the option [severity] "Less than or equal to" enabled.

  • Fixed issue in Maintenance module where user could not input a Description for Automated Responses.

  • Fixed issue where under certain conditions, when an escalation procedure was called and the message was an unanswered inquiry message, the procedure would not run as expected.

  • Fixed issue where the System Configuration data was not being removed after an install.

QRemote Control

Version 4.13

February 5, 2026

  • Incremental release to match the QMessage Monitor release.

Back to Top

 

Clearswift


Secure Email Gateway

Version 6.2.1

February 5, 2026

NOTE:

Version 6.2.1 is a release containing the fix below.

For Japanese Release Notes, click here.

Fixes
  • Updated the Avira Anti-Virus Cloud Lookup component to ensure continued operation after 10 March 2026.

    For more information, see this knowledge article in the Fortra Support Portal.

Secure Exchange Gateway

Version 6.2.1

February 5, 2026

NOTE:

Version 6.2.1 is a release containing the fix below.

For Japanese Release Notes, click here.

Fixes
  • Updated the Avira Anti-Virus Cloud Lookup component to ensure continued operation after 10 March 2026.

    For more information, see this knowledge article in the Fortra Support Portal.

Secure ICAP Gateway

Version 6.2.1

February 5, 2026

NOTE:

Version 6.2.1 is a release containing the fix below.

For Japanese Release Notes, click here.

Fixes
  • Updated the Avira Anti-Virus Cloud Lookup component to ensure continued operation after 10 March 2026.

    For more information, see this knowledge article in the Fortra Support Portal.

Secure Web Gateway

Version 6.2.1

February 5, 2026

NOTE:

Version 6.2.1 is a release containing the fix below.

For Japanese Release Notes, click here.

Fixes
  • Updated the Avira Anti-Virus Cloud Lookup component to ensure continued operation after 10 March 2026.

    For more information, see this knowledge article in the Fortra Support Portal.

Back to Top

 

Digital Guardian


Linux

Version: 12.1.0

February 2026

New Features
  • Certification for Additional Kernels

This table lists the additional certified Linux kernels for Red Hat Enterprise Linux (RHEL) and Ubuntu in this release. Refer to the Agent for Linux User's Guide for details about the packages required to support the new kernel versions for the Agent. Refer to Agent_for_Linux_v12.x.x_and_Later_RHEL_Certified_Environments and Agent_for_Linux_v12.x.x_and_Later_Ubuntu_Certified_Environments for the complete lists of supported RHEL and Ubuntu kernels.

Distribution

Version

Architecture

Kernel

RHEL 10.1 64-Bit kernel-6.12.0-124.35.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.31.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.29.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.28.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.27.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.21.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.20.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.16.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.13.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.11.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.9.1.el10_1
RHEL 10.1 64-Bit kernel-6.12.0-124.8.1.el10_1
RHEL 10.0 64-Bit kernel-6.12.0-55.58.1.el10_0
RHEL 10.0 64-Bit kernel-6.12.0-55.55.1.el10_0
RHEL 10.0 64-Bit kernel-6.12.0-55.54.1.el10_0
RHEL 10.0 64-Bit kernel-6.12.0-55.52.1.el10_0
RHEL 10.0 64-Bit kernel-6.12.0-55.50.1.el10_0
RHEL 10.0 64-Bit kernel-6.12.0-55.48.1.el10_0
RHEL 10.0 64-Bit kernel-6.12.0-55.47.1.el10_0
RHEL 9.7 64-Bit kernel-5.14.0-611.30.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.27.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.26.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.24.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.20.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.16.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.13.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.11.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.9.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.8.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.7.1.el9_7
RHEL 9.7 64-Bit kernel-5.14.0-611.5.1.el9_7
RHEL 9.6 64-Bit kernel-5.14.0-570.86.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.84.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.81.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.79.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.77.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.76.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.73.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.72.1.el9_6
RHEL 9.6 64-Bit kernel-5.14.0-570.69.1.el9_6
RHEL 9.4 64-Bit kernel-5.14.0-427.109.1.el9_4
RHEL 9.4 64-Bit kernel-5.14.0-427.108.1.el9_4
RHEL 9.4 64-Bit kernel-5.14.0-427.107.1.el9_4
RHEL 9.4 64-Bit kernel-5.14.0-427.106.1.el9_4
RHEL 9.4 64-Bit kernel-5.14.0-427.104.1.el9_4
RHEL 9.4 64-Bit kernel-5.14.0-427.103.1.el9_4
RHEL 9.4 64-Bit kernel-5.14.0-427.102.1.el9_4
RHEL 8.10 64-Bit kernel-4.18.0-553.104.1.el8_10
RHEL 8.10 64-Bit kernel-4.18.0-553.100.1.el8_10
RHEL 8.10 64-Bit kernel-4.18.0-553.97.1.el8_10
RHEL 8.10 64-Bit kernel-4.18.0-553.94.1.el8_10
RHEL 8.10 64-Bit kernel-4.18.0-553.92.1.el8_10
RHEL 8.10 64-Bit kernel-4.18.0-553.89.1.el8_10
RHEL 8.10 64-Bit kernel-4.18.0-553.87.1.el8_10
Ubuntu 24.04 64-Bit linux-image-6.14.0-37-generic
Ubuntu 24.04 64-Bit linux-image-6.8.0-94-generic
Ubuntu 24.04 64-Bit linux-image-6.8.0-90-generic
Ubuntu 22.04 64-Bit linux-image-6.8.0-94-generic
Ubuntu 22.04 64-Bit linux-image-6.8.0-90-generic
Ubuntu 22.04 64-Bit linux-image-6.8.0-88-generic
Ubuntu 22.04 64-Bit linux-image-5.15.0-168-generic
Ubuntu 22.04 64-Bit linux-image-5.15.0-164-generic
Ubuntu 22.04 64-Bit linux-image-5.15.0-163-generic
Fixes
  • Resolved an issue where Linux servers with the DG Agent installed could get stuck during reboot. This has been optimized to improve the reboot process, enhancing restart reliability and reducing reboot time when the agent is present.

NOTE: For information about Process Flag File Changes, refer to Digital_Guardian_12_1_0_Agent_for_Linux_Release_Notes > Resource File Changes available on the Fortra Support Portal.

Server (DGMC)

Version: 9.1.0

February, 2026

New Features
  • This release introduces the Control Policies feature to simplify policy creation and improve usability. Previously, all policies and rules were managed together in a single dropdown. Now, policies are split into two tabs: Advanced Policies and the new Control Policies. Control Policies provides a cleaner, more intuitive interface for creating less complex policies and rules, offering greater flexibility, clarity, and a more efficient user experience.

    For complete installation instructions and navigation details for Control Policies, refer to the Digital Guardian Control Policies Guide v1.0 on Fortra Support Portal.

    NOTE: Control Policies are primarily intended for new DLP customers. Existing customers must manually migrate their current policies and rules, as automated migration is not currently available and requires careful planning.
  • DGMC Now supports DCS label integration within policy rules. User can now import a DCS label schema into the console and create DLP control rules against any level of DCS labels. This enhancement improves interoperability between Data Classification and DLP components, reduces manual configuration, and ensures consistent enforcement of classification policies across the environment.

  • The User tab in Agent Status displays both local and domain users, providing detailed information and functionalities for user management. It helps troubleshoot missing user policies and track the users reported as logged-in by the agent, making easier for customers.

  • This release introduces safeguards to ensure the Reset ALL Rule Parameters to Default button on the Policy → Rule Parameters tab in DGMC is used intentionally. These updates prevent accidental resets and clearly communicate the impact of the action. The reset button is now configurable (hidden by default), its label has been updated to 'Reset ALL Parameters to Default', and the Save icon has been replaced with a POST label to indicate that rule parameter changes apply to all policies using the rule. Refer to Digital Guardian Management Console User Guide v9.1.0 on Fortra Support Portal for more details.

  • Users now see an updated main menu header and login banner that align with the company’s current product portfolio names. These changes deliver a consistent, modern visual experience across DGMC. The main menu header and login banner display the new images, the login Terms & Conditions text has been updated, and the browser tab text now reflects the latest branding.

Fixes
  • Resolved an issue that caused the Alert reports to fail when the selected timeframe was greater than 120 days.

  • Resolved an issue where orphan component lists still appeared on the policy page.

  • Resolved a background import issue that caused incorrect BIN files to be processed during async imports.

  • Resolved an issue where the STG_APPLICATION_RULE table still used an 80-character rule name limit, causing ETL failures when longer rule names were entered.

  • Resolved an issue where dgscope field names in DGRuleMeta.xml did not match DGRule30.xsd, preventing proper schema alignment.

  • Resolved an issue where the rule priority page stayed in edit mode after saving changes instead of returning to normal view.

  • Resolved an issue where ETL jobs did not run automatically and triggered divide-by-zero errors despite appearing successful.

  • Resolved an issue that caused the Verdasys_Export_Data job to fail and prevented alerts, processes, and console logs from exporting to the SIEM system.

  • Resolved an issue where long-running content-server imports showed incorrect user and timestamp information in console activity tracking.

  • Resolved an issue where Users events are missing in custom report after adding "Surname", "Given Name" and "Department Name" fields.

  • Resolved an issue where DGMC could not map MIP labels from ARC Lite due to missing DG tag mapping.

  • Resolved an issue where new DGWIP domain flags (TLS_12_ONLY and TLS_13_ONLY) were not recognized until manually added to the DGMC web.config file.

  • Resolved an issue where the “Reset Non-Communicating Agent Status” feature stopped resetting after 'X' days.

  • Resolved an issue where the pagination popup did not close, preventing users from switching pages in the DG Finder.

  • Resolved an issue where policies created in Policy Manager failed to publish due to missing or unrecognized severity parameters.

Network DLP Appliance

Version: 13.1.0

February, 2026

New Features
  • The nDLP discovery engine now provides improved scalability and significantly faster scan times in large environments. This update optimizes the discovery process to deliver seamless scalability, enhanced performance, and reduced latency. By default, all new discovery scans now run using the optimized engine.

    NOTE: When upgrading to version 13.1, the following behavior changes apply to discovery scans:
    The system does not retain statistics for scans created before the upgrade. The user needs to rerun those scans to generate new statistics. Scans that are paused before the upgrade cannot resume after upgrading. Stop all active or paused scans before upgrading.

    Administrators can revert to the previous scan model if necessary. For full configuration instructions, refer to DigitalGuardian Appliance Administrators Guide v13.1.0 > Discovery Engine Configuration (Version 13.1.0 and Later) available on Fortra Support Portal.

  • This release introduces parallel (co-existing) authentication keys for SharePoint and OneDrive integrations to ensure a smooth, uninterrupted key rotation. The following changes apply:

    • Existing keys will remain active until the transition completes.

    • Current keys are planned to expire in Q2 2026. Support will notify customers in advance of the expiration.

    • Customers do not need to take any action to start using the new keys.

    IMPORTANT: To continue using the SharePoint and OneDrive integrations, customers must upgrade to version 13.1 or later before the existing keys expire.
Fixes
  • Resolved an issue where ICAP requests from some applications could exceed the maximum URL length and fail.

  • Resolved an issue where nDLP Appliance Manager version 13.0 did not list connected agents, even though they were successfully registered and connected.

  • Resolved an issue where the Data Discovery incidents list did not sort correctly by file size when filters were applied.

  • Resolved an issue where the nDLP Appliance incident details view truncated filenames that contained spaces.

  • Resolved an issue where nDLP was unable to extract MIP labels for certain Excel files (Excel 2021+ XML format).

  • Resolved an issue where nDLP Appliance did not detect Microsoft Information Protection (MIP) labels on PDF and PNG files.

  • Resolved an issue where nDLP Data at Rest inventory scans could not complete or update logs correctly when scanning DFS SMB shares.

  • Resolved an issue where the NDLP policy option “Apply this Policy when ALL email recipient matches ANY of the above filters” did not save correctly in the user interface.

Back to Top

 

FileCatalyst


FileCatalyst Direct

Version 4.0.2 - Build 668

February 27, 2026

Added
  • All - Modernized look and feel
  • All - Various documentation updates.
  • All - Updated JRE/JDK packaged with application to Zulu OpenJDK.
  • Load Balancer - Implemented the ability to enable SSL connections on FileCatalyst LoadBalancer.
  • Server, HotFolder, and TransferAgent - Added new SSL keystore system for applications to accept new SSL certificates for connections.
  • Server, HotFolder, and TransferAgent - Added ability to view, add, and remove SSL certificates into application.
Fixes
  • Central - Fixed the issue where old LDAP configurations in FileCatalyst Central would not properly import on upgrades
  • Central - Fixed issue where transfers would repeatedly cancel if Multi-Client Manager, rescans, and the auto transfer mode were enabled.
  • Server - Fixed issue where Server admin could hang if an admin user cancelled a speed test
  • Server - Fixed issue where URL unsafe characters would cause file lookups to fail in EFS drivers
  • Server - Fixed issue where admins could not apply user default settings in the Server HTML admin
  • Server - Fixed issue where Server transfer data reports would not properly merge checksum fields if there was an error then successful transfer.•

  • Server - Fixed issue where home directory failed to auto-populate when selecting an EFS storage.

  • Server - Fixed issue where some valid email addresses would be rejected by the validator.

  • Server - Fixed issue where URL unsafe characters would fail to download from Azure Blob EFS storage.

  • Server - Fixed issue where cancelling S3 access speed tests would cause the Server HTML admin to hang.

  • TransferAgent - Fixed issue where TransferAgent clients were unable to set the number of clients for a connection.
  • TransferAgent - Fixed issue where TransferAgent clients test connection would fail on HTTP when servlet URLs were provided.

  • TransferAgent - Fixed issue where Sites would not appear in the test connection dropdown and test connection page.

  • Central, Server - Fixed issue where FileCatalyst Central would not collect all of the reports from FileCatalyst Server.
  • All Clients - Fixed issue Server side post processing would trigger before a WREP command.
  • All Clients - Fixed issue certain transfer configuration would result in cyclic ABOR commands.

  • All - Fixed issue force file ownership feature would sometimes hang on user/group profile lookups.
  • All - Multiple security fixes.

Back to Top

 

Powertech


BoKS Manager

Version 9.0

February 27, 2026

Server s-9.0.0.3
New Features
  • Added support for RHEL 10 for Master & Replica.

Version 8.1

February 3, 2026

Client c-8.1.0.27
New Features
  • boksinfo now contains information about SELinux domains.

Enhancements
  • Server Agent reports 4-digit version number.

Fixes
  • The Logout message is logged twice for SSH sessions when kslog is enabled.

  • Incorrect error message in cadm when a non-registered host is specified.

  • Added missing tls/ecgroups definition.

  • Missing SELinux process domains in boksinfo.

  • Sudo and Suexec errors need to be more descriptive.

  • Missing fields in dictionary file.

  • bokssetup error with multiple sshd* users in /etc/passwd.

  • BoKS passwd fails with long usernames.

  • ssh(1) command injection via ProxyCommand (CVE-2025-61984).

Security Scan for IBM i

Version 3.5.1

February 12, 2026

Enhancements
  • Changed file name when sending a report scan to show name and company.

Fixes
  • Fixed an issue with the "Send a Security Scan" option not including customer detail.

  • Updated URLs in product to reflect the new power.fortra.com subdomain.

  • There is no longer version a of the product.

  • Java version has been updated to Java 21.

SIEM Agent for IBM i

Version 4.9

February 5, 2026

Enhancements
  • Powertech Antivirus for IBM i is now available as an Event Source.

  • For new installs, we now default to using the delimiter method for *NETWORK outputs with *TCP protocol. The delimiter has been set to the new line character. Users can override the delimiter string in PSASYP, for example, to the null character.

  • A process to export the SIEM Agent configuration from one system and import it into another system has been added to the product with the new commands PSAEXPCFG and PSAIMPCFG.

  • The text of the "Scan exit program action" Event Text was modified to include the path of the file affected by the action. (This Event is issued when a malware scanner such as Powertech Antivirus for IBM i's identifies a file as infected.)

  • Two new commands PSAEXPCFG and PSAIMPCFG have been added to the product and to the Utilities Menu.

  • License related messages are now part of of the SYSMSG Event Source.

  • Updates have been made to the SIEM Agent Installation Guide. Central Admin 2.32 will be included as part of an installation.

  • The "Monitoring Powertech Antivirus with SIEM Agent” help topic in the User Guide has been updated to explain how to use the new *ANTIVIRUS type of event source to monitor Powertech Antivirus.

  • AUDIT Event Source supports changes for 7.6:

    • CP “Change to user profile”: Changes to user profile MFA attributes are reflected in T:CP data.

    • DS “Service Tools User ID and Attribute Changes”: The existing entry type includes new data in a previously reserved area for MFA attribute changes.

    • GR “Generic record”: Introduces a new subtype F, with *USAGEWARN.

    • SV “System values”: Changes to MFA-related system-wide security attributes are reflected, within the existing subtype for security attributes.

    • PW “Password failures”: Authentication failures due to failed TOTP or MFA are recorded in a new subtype G.

    • Changes to DDM attributes result in the corresponding SM journal entry having an entry type (subtype) of "M", instead of being grouped with DRDA changes under "D".

Fixes
  • New IBM i 7.5 audit journal subtypes for entries T:M8, T:PS, T:VP were missing and have been added.

  • SIEM Agent jobs with function USR-AUDIT sometimes failed as a result of an MCH3402 error. This has been fixed.

Back to Top

 

TeamQuest


Automated Analytics

Version 11.3.44

February 23, 2026

Enhancements
  • Upgraded Apache Tomcat to 9.0.112.

  • Added user auditing capabilities to Automated Analytics.

Fixes
  • Fixed missing images in exported PDF.

PostgreSQL

Version 16.11

February 5, 2026

Enhancements
  • Upgraded PostgreSQL to 16.11.

TeamQuest Administration Console

Version 11.4.14

February 5, 2026

Enhancements
  • Updated OpenSSL to v3.4.3.

  • Updated Apache HTTPD to v2.4.66.

TeamQuest Manager

Version 11.4.20

February 5, 2026

Enhancements
  • Validated TeamQuest Manager on Windows Server 2025.

  • Updated Apache HTTPD to v2.4.66.

  • Updated OpenSSL to v3.4.3.

VCM

Version 2.24

February 23, 2026

Enhancements
  • Validated VCM Collector on Windows Server 2025.

  • Upgraded ActiveMQ to 6.1.8.

  • Added user auditing capabilities to VCM.

  • Added authentication to Collector API.

  • Upgraded PostgreSQL to 17.7.

  • Upgraded Apache Spark to 3.5.7.

  • Upgraded Apache Storm to 2.8.3.

Fixes
  • Addressed information disclosure vulnerability using stack trace.

Known Limitations and Unresolved Items from Final Testing
  • Upgrading the Windows Collector will revert the ZookeeperConnectionString back to the default value. Workaround: Add a step to your automated installation to save the current ZookeeperConnectionString and reinstate it after the upgrade of the Collector.

  • The VCM Collector is not currently supported on SLES 15 (v5.3 kernel).

  • Restarting the VCM services while logged in to the VCM UI may result in an “OOPS” error when logging out and back in too quickly. Workaround: Wait a minute or two before logging back in.

  • The Collector button may not be present after a new installation due to a race condition. Workaround: Restarting the services will enable the button. Use /opt/vityl/utils/vcmctl.sh restart to restart the services.

  • If you are upgrading from VCM version 2.22 or earlier to VCM 2.24, you must update the protocol from HTTP to HTTPS for all VCM Metrics API data sources after completing the installation.

Vityl Monitor

Version 11.4.15

February 5, 2026

Enhancements
  • Validated Vityl Monitor on Windows Server 2025.

  • Upgraded Apache Tomcat to 9.0.112.

Back to Top

 

Human Risk Management (prior Terranova Security)


Version: 1.122

February 18, 2026

Enhancements
  • A new report titled “Total Training Time” is now available under Standard Reports - Courses. This report displays the total amount of time users have spent in training during a selected period or on specific courses. It includes all users, even those who no longer have access to the training, and accounts for time spent on both completed and in-progress courses.

Back to Top

 

Titus


DCS for Windows

Version 6.1.1

February 13, 2026

Fixes
  • Resolved issue where the "Force Select On Save" application setting was being ignored during a save operation.
  • Resolved issue in Microsoft Outlook where body tags that should have appeared in the footer of each message always appeared at the end of the entire message.
  • After selecting parent values in multiple selection fields, there were delays in loading child values. This issue has been resolved.

Back to Top

 

Secure Collaboration (Vera)


Version 3.25.0

February 2026

Enhancements
  • Vera SaaS

    • Tomcat has been upgraded from the Rocky/RHEL-packaged Tomcat 9.0.87 to 9.0.106, reducing exposure to known Tomcat vulnerabilities while keeping the connector deployment and upgrade experience consistent across environments.

  • Windows Client

    • Secure Collaboration (Vera) extends its existing AutoCAD integration to support AutoCAD 2024.

    • Secure Collaboration (Vera) extends its existing Nitro PDF support to deliver full functionality with Nitro PDF 14 on Windows, ensuring complete compatibility across all secure collaboration workflows.

  • Mac Client

    • Secure Collaboration (Vera) adds support for saving changes to files protected by Advanced Access Control on macOS, allowing users to directly save updates to secured documents.

Fixes
  • Vera SaaS

    • Fixed an issue where Vera connector servers were flagged during vulnerability scans. The connector and server logging stack were updated to replace Apache Log4j 1.x with Log4j 2 and to update SLF4J/Logback dependencies, remediating the identified Log4j 1.x vulnerabilities.

    • Fixed an issue where Google Chrome intermittently failed to detect the installed Vera desktop application. When opening a secured document, affected users were repeatedly prompted to download and install Vera even though the application was already installed and running.

      IMPORTANT: For more information, refer to the Chrome and Edge Local Network Access Policy Configuration Guide on the Secure Collaboration (Vera) Admin Portal.
  • Windows Client

    • Fixed an issue in Adobe Acrobat where user can insert or replace pages from a secured PDF into an unsecured or secured file. This operation is now blocked, and users see a message indicating that the action is not allowed on secured files.

Back to Top