Tenable One Identity Exposure 2026 On-Premises Release Notes
Tip: You can subscribe to receive alerts for Tenable documentation updates.
These release notes are listed in reverse chronological order.
Tenable One Identity Exposure 3.93.7 (2026-11-16)
-
After upgrading, run the Indicators of Attack script again on the domain controllers, so they get the updated events listener with the DNS fix.
-
You no longer need to stop the Security Engine Node services before upgrading the Storage Manager.
-
Before upgrading, make sure your custom TLS certificates and their CA use RSA keys of at least 2048 bits. Node.js 24 refuses shorter keys.
Tenable One Identity Exposure version 3.93.7 contains the following bug fixes:
| Bug Fixes |
|---|
| Storage Manager upgrades no longer fail when the Security Engine Node is still connected to the database, and a failed attempt no longer leaves the database in single-user mode. |
| The installer no longer refuses to start when the only pending file operations are routine clean-up by other software, such as the Microsoft Edge updater. A real pending restart still stops it, and the message now says what is pending. |
| Indicators of Attack no longer turn on the DNS Analytical event log on domain controllers running Windows Server 2022 or later, which could slow down DNS on domain controllers that are also DNS servers. Upgrading removes the unreleased DNS Enumeration indicator from existing configurations, and uninstalling Indicators of Attack now undoes the event log changes. |
| Syslog and email alerts sent through Secure Relays no longer stop for every relay when one relay is removed, reinstalled or stays offline. Alerts waiting for a relay that is gone are now dropped, so the other relays keep receiving theirs. |
| Cancelling or failing a Directory Listener installation no longer leaves Active Directory data collection stopped. |
| The full security check no longer takes a very long time, or never finishes, on large domains because of the password policy indicator. |
| Security Engine Node installations and upgrades are faster. |
| Updated third-party libraries to fix known vulnerabilities. |
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.93.6 | 3.93.7 |
| C++ 2015-2022 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.33.26523 | 10.0.14 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 24.22.1.0 | 24.22.1.0 |
| Erlang OTP | 27.3.4.19 | 27.3.4.19 |
| Rabbit MQ | 4.2.9 | 4.3.7 |
| SQL Server | 15.0.4470.1 | 15.0.4500.2 |
| OpenSSL | 4.0.1 | 4.0.3 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.20.0 | 8.23.0 |
| 7-Zip | 19.00 | 26.05 |
| IoA Events Listener | 2.0.1 | 2.0.3 |
Tenable One Identity Exposure 3.77.19 (2026-11-16)
-
After upgrading, uninstall the Indicators of Attack script from the domain controllers (Register-TenableIOA.ps1 -Uninstall) and install it again, so they get the updated events listener with the DNS fix.
-
You no longer need to stop the Security Engine Node services before upgrading the Storage Manager.
-
Before upgrading, make sure your custom TLS certificates and their CA use RSA keys of at least 2048 bits. Node.js 24 refuses shorter keys.
Tenable One Identity Exposure version 3.77.19 contains the following bug fixes:
| Bug Fixes |
|---|
| Storage Manager upgrades no longer fail when the Security Engine Node is still connected to the database, and a failed attempt no longer leaves the database in single-user mode. |
| The installer no longer refuses to start when the only pending file operations are routine clean-up by other software, such as the Microsoft Edge updater. A real pending restart still stops it, and the message now says what is pending. |
| Indicators of Attack no longer turn on the DNS Analytical event log on domain controllers running Windows Server 2022 or later, which could slow down DNS on domain controllers that are also DNS servers. Upgrading removes the unreleased DNS Enumeration indicator from existing configurations, and uninstalling Indicators of Attack now undoes the event log changes. |
| Syslog and email alerts sent through Secure Relays no longer stop for every relay when one relay is removed, reinstalled or stays offline. Alerts waiting for a relay that is gone are now dropped, so the other relays keep receiving theirs. |
| Cancelling or failing a Directory Listener installation no longer leaves Active Directory data collection stopped. |
| The full security check no longer takes a very long time, or never finishes, on large domains because of the password policy indicator. |
| Security Engine Node installations and upgrades are faster. |
| Updated third-party libraries to fix known vulnerabilities. |
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.77.18 | 3.77.19 |
| C++ 2015-2022 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.33.26523 | 10.0.14 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 24.22.1.0 | 24.22.1.0 |
| Erlang OTP | 27.3.4.19 | 27.3.4.19 |
| Rabbit MQ | 4.2.9 | 4.3.7 |
| SQL Server | 15.0.4460.4 | 15.0.4500.2 |
| OpenSSL | 3.6.1 | 4.0.3 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.19.0 | 8.23.0 |
| 7-Zip | 19.00 | 26.05 |
| IoA Events Listener | 1.0.1 | 1.0.3 |
Tenable One Identity Exposure 3.93.6 (2026-10-30)
-
Before upgrading, make sure your custom TLS certificates and their CA use RSA keys of at least 2048 bits. Node.js 24, which this release installs, refuses shorter keys.
-
After upgrading, uninstall and reinstall the Indicators of Attack script on the domain controllers (Register-TenableIOA.ps1 -Uninstall, then install again). The upgrade alone keeps the old IoA events listener.
-
After a successful upgrade, you can delete the upgrade backup folder C:\Tenable\Tenable.old.
Tenable One Identity Exposure version 3.93.6 contains the following bug fixes:
| Bug Fixes |
|---|
| Fixed a security issue in the Indicators of Attack events listener that let an account with write access to the IoA configuration run commands as SYSTEM on the domain controller. To apply the fix, uninstall and reinstall the IoA script after upgrading. |
| Fixed security issues where specially crafted API queries could slow down the service. |
| Fixed a security issue where a failed Secure Relay installation wrote the linking key to its log file. |
| Fixed a security issue where error messages shown when activating Tenable Cloud features revealed details of internal server requests. |
| Fixed an issue where some accounts deleted from Active Directory were still counted against the license, so license consumption could be higher than the active users shown on the dashboard. Deleted accounts are now removed correctly, and the object classes that an earlier update changed by mistake are repaired. |
| Fixed an issue where testing the connectivity of a domain timed out. |
| The IoA installation script now locates the IOA folder through the SYSVOL share published by the PDC emulator, and falls back to the administrative share only when the SYSVOL share cannot be reached. Previously, when the domain name was supplied instead of a domain controller name, the script could end with an error even though the IoA module had been deployed correctly. If the folder still cannot be read during installation, the script now reports a clear warning instead of an error, and it warns when the -DomainControllerAddress parameter is given a domain name. |
| Fixed an issue where the Keep potential false positives for orphan keys option of the Shadow Credentials indicator of exposure did not apply to every orphan key credential whose device cannot be verified, including the all-zero device GUID that Entra ID writes back for FIDO2/passkey enrolments. The option is now applied using the configuration of the domain the checked user belongs to, and a key credential suppressed by that option no longer hides a genuinely orphan one declared after it on the same account. |
| The IoA listener launcher script no longer starts PowerShell with the execution policy set to Bypass. |
| Fixed an issue where the Dangerous Trust Relationships indicator of exposure incorrectly flagged intra-forest parent-child trusts as external when the trust used the legacy Windows attributes TREE_PARENT or TREE_ROOT instead of the WITHIN_FOREST flag. The indicator now correctly identifies these trusts as intra-forest by verifying their presence in the forest's Configuration partition. |
| Fixed an issue where the indicator of exposure that detects password weaknesses (C-PASSWORD-HASHES-ANALYSIS) kept reporting a Password Reuse within Domain deviance after the accounts involved had stopped sharing a password. These deviances are now cleared once the accounts no longer share a password. |
| Fixed an issue where HC-PLATFORM-RELAY-UP and HC-PLATFORM-RELAY-VERSION health check syslog alerts were sent to every syslog destination subscribed to that health check, regardless of which relay triggered the alert. These alerts are now delivered only to the syslog destinations linked to the relay that generated them. Alerts for HC-PLATFORM-ALERTING and non-relay services are still broadcast. |
| The Privileged Analysis status on the Domains page no longer shows a failure when the network drops the reply to the Secure Relay's endpoint mapper port lookup while privileged data collection works, and the connection and permission checks now complete faster. The Privileged Analysis and domain reachability health checks now report an undetermined state, instead of a failure, when the DRSUAPI dynamic port cannot be determined or a check runs out of time. A refused TCP connection is now correctly reported as unreachable. |
| Fixed an issue where the customization pane of an indicator in a security profile could not be opened when the interface language was Japanese. |
| Fixed an issue where, with more than one security profile, every Active Directory weakness appeared once per profile in Exposure Management. Tenable One Identity Exposure now sends only the weaknesses of the Tenable security profile. |
| Fixed an issue where a Storage Manager upgrade could fail when SQL Server keeps its data inside the Tenable One Identity Exposure installation folder, and a retried upgrade did not bring that data back. The upgrade now always restores the SQL Server data before it continues. |
| Fixed an issue where an upgrade of a Storage Manager whose SQL Server had been upgraded in place (for example, from SQL Server 2017 to 2019 by an earlier installer) could not find the SQL Server data, failed, and could leave the database in the Tenable.old backup folder. The upgrade now moves such an instance into the standard folder before making other changes, and a failed upgrade now restores the installation into its original folder and completes every step. |
| Fixed an issue where the Secure Relay could fail to read an Indicators of Attack event file while the domain controller was still writing it. The read was refused by Windows, the file was abandoned after a few retries, and the events it held were discarded. IoA event files are now read in a way that tolerates the domain controller writing them, and a file that is read while incomplete is read again instead of being processed partially. |
| Fixed an issue where Exposure Center could display Active Directory findings with no impacted assets after a batch of Active Directory objects was refused during transfer to the cloud and retried indefinitely, which blocked the queue. Batch sizes now match what the ingest service accepts, and retries are bounded so the queue keeps moving. |
| Fixed an issue where, during an upgrade from 3.77, endpoint security software could delete files from the Node.js modules on the Security Engine Node, so the upgrade did not complete. The deprecated library that these products flagged has been removed. |
| Fixed an issue where dashboard widgets based on Indicators of Exposure could show 0 deviances and a compliance score of 100, while the Indicators of Exposure page correctly showed active deviances. This affected any security check whose deviance count had not changed for over a month, because the last recorded value for that check was removed by the monthly clean-up. The clean-up now always keeps the most recent value for each series. |
| Fixed an issue where rolling back a Security Engine Node installation left an IIS rule behind, and every later installation attempt failed with error 1603 (Cannot add duplicate collection entry). The installer now replaces IIS settings that already exist and removes them on rollback. |
| Fixed an issue where some active users did not appear in User Accounts Management. Users with an assigned role are now included in the Users list, so every account that can access the platform can be reviewed and audited. |
| Fixed an issue where the Golden Ticket indicator could raise a false alert when a routine Kerberos ticket renewal was followed by use of that ticket and the source host's DNS record is stored in the ForestDnsZones partition. Tenable One Identity Exposure now includes ForestDnsZones when it checks which objects still exist, and matches ticket renewals by IP address as well as host name. Hosts whose DNS records are in ForestDnsZones also now show their names in attack alerts instead of Unknown. |
| Fixed an issue where the IoA listener on each domain controller wrote its logs into SYSVOL, where they could cause replication issues for the IoA Group Policy. You can now keep the listener logs on each domain controller instead, the logs are capped in size, and a newer deployment script updates the listener already installed on the domain controllers. Saving the Indicators of Attack page no longer switches off the Dedicated SMB share mode. |
| Fixed an issue where the indicator of exposure that reports user accounts whose password has never been changed (C-USER-PASSWORD) flagged accounts whose password had just been reset by an administrator with the option requiring a change at the next logon. Because that option clears the last password change date in Active Directory, those accounts were reported as though their password had never been changed. They are no longer reported. |
| Fixed an issue where the download link in a scheduled report email could fail with Unable to find report, because the same report was sometimes generated and emailed more than once and only the latest link stayed valid. Each scheduled report is now generated and emailed once. |
| Fixed an issue where Password Reuse within Domain and Password Reuse within Domain by a Privileged Account findings could remain open after the accounts they listed changed their passwords, even after a recrawl. These findings now clear automatically within a day of the next completed crawl. |
| Fixed an issue where the engine that evaluates Indicators of Exposure kept several CPU threads busy while it had nothing to process, on any platform where Active Directory changes at least once a minute. It now waits for new changes instead, so CPU usage drops while it is idle. On-premises, this is the high CPU usage seen on the Security Engine Node. |
Advisory: For details about the security fixes in this release, see TNS-2026-34.
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.93.5 | 3.93.6 |
| C++ 2015-2022 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.28.26269 | 8.0.33.26523 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 20.20.2.0 | 24.22.1.0 |
| Erlang OTP | 26.2.5.21 | 27.3.4.19 |
| Rabbit MQ | 4.0.9 | 4.2.9 |
| SQL Server | 15.0.4470.1 | 15.0.4470.1 |
| OpenSSL | 4.0.1 | 4.0.1 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.20.0 | 8.20.0 |
Tenable One Identity Exposure 3.77.18 (2026-10-30)
-
Before upgrading, make sure your custom TLS certificates and their CA use RSA keys of at least 2048 bits. Node.js 24, which this release installs, refuses shorter keys.
-
After upgrading, uninstall and reinstall the Indicators of Attack script on the domain controllers (Register-TenableIOA.ps1 -Uninstall, then install again). The upgrade alone keeps the old IoA events listener.
-
After a successful upgrade, you can delete the upgrade backup folder C:\Tenable\Tenable.old.
Tenable One Identity Exposure version 3.77.18 contains the following bug fixes:
| Bug Fixes |
|---|
| Fixed a security issue in the Indicators of Attack events listener that let an account with write access to the IoA configuration run commands as SYSTEM on the domain controller. To apply the fix, uninstall and reinstall the IoA script after upgrading. |
| Fixed security issues where specially crafted API queries could slow down the service. |
| Fixed a security issue where a failed Secure Relay installation wrote the linking key to its log file. |
| Fixed a security issue where error messages shown when activating Tenable Cloud features revealed details of internal server requests. |
| Indicator of Exposure (IoE) Last Password Change on KRBTGT account remediation script has been updated. |
| IoA listeners now automatically detect PDC Emulator FSMO role transfers and restart with the correct identity, eliminating the need for manual intervention across all domain controllers. |
| The Password Reuse within Domain indicator of exposure now correctly resolves the deviance when a user password is changed to a different one. |
| Fixed an issue where the Keep potential false positives for orphan keys option of the Shadow Credentials indicator of exposure did not apply to every orphan key credential whose device cannot be verified, including the all-zero device GUID that Entra ID writes back for FIDO2/passkey enrolments. The option is now applied using the configuration of the domain the checked user belongs to, and a key credential suppressed by that option no longer hides a genuinely orphan one declared after it on the same account. |
| IoA deployment scripts now correctly output audit policies section. |
| Fixed an issue where the password reuse indicator of exposure was incorrectly raised on internal DNS partition objects (ForestDnsZones, DomainDnsZones) instead of only on the actual domain. Customers may have seen spurious password reuse deviances attributed to these non-root objects. These false positives are no longer generated. |
| GoldenTicket Indicator of Attack (IoA) — Prevents duplicate Golden Ticket alerts when a single suspicious 4769 correlates with multiple 4624 logon events within the one-hour window. Each suspicious 4769 now raises at most one alert per profile. |
| The scheduled task that launches the Indicators of Attack (IoA) event listener on Domain Controllers has been upgraded from Low priority to Normal priority. This resolves an issue where heavily loaded DCs could delay the script launch by several hours, potentially causing gaps in attack detection coverage. |
| Fixed an issue where the Dangerous Trust Relationships indicator of exposure incorrectly flagged intra-forest parent-child trusts as external when the trust used the legacy Windows attributes TREE_PARENT or TREE_ROOT instead of the WITHIN_FOREST flag. The indicator now correctly identifies these trusts as intra-forest by verifying their presence in the forest's Configuration partition. |
| The IoA events listener now detects and automatically recovers from silent failures, where event logging stops without triggering error alerts (for example, during security patch installations). If no events are detected for 60 minutes, subscriptions are automatically restarted. Requires an IoA reinstall. |
| The Shadow Credentials indicator of exposure now flags the WHfBTools module as deprecated in its remediation guidance. The module calls the Azure AD Graph API, which Microsoft retired in September 2025, so it no longer works. The manual procedure of clearing the msDS-KeyCredentialLink attribute with Set-ADUser or Set-ADComputer is unchanged. |
| Fixed an issue where dashboard widgets based on Indicators of Exposure could show 0 deviances and a compliance score of 100, while the Indicators of Exposure page correctly showed active deviances. This affected any security check whose deviance count had not changed for over a month, because the last recorded value for that check was removed by the monthly clean-up. The clean-up now always keeps the most recent value for each series. |
| Fixed an issue where an upgrade of a Storage Manager whose SQL Server had been upgraded in place (for example, from SQL Server 2017 to 2019 by an earlier installer) could not find the SQL Server data, failed, and could leave the database in the Tenable.old backup folder. The upgrade now moves such an instance into the standard folder before making other changes, and a failed upgrade now restores the installation into its original folder and completes every step. |
Advisory: For details about the security fixes in this release, see TNS-2026-34.
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.77.17 | 3.77.18 |
| C++ 2015-2022 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.25 | 8.0.33.26523 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 20.20.2.0 | 24.22.1.0 |
| Erlang OTP | 26.2.5.18 | 27.3.4.19 |
| Rabbit MQ | 4.0.9 | 4.2.9 |
| SQL Server | 15.0.4460.4 | 15.0.4460.4 |
| OpenSSL | 3.6.1 | 3.6.1 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.19.0 | 8.19.0 |
Tenable One Identity Exposure 3.93.5 (2026-06-23)
-
Introduced granular time filtering for Indicators of Attack, enhancing the existing date-only filter to allow users to specify the hour, minute, and second, and provide the IoA link in the syslog alert.
Tenable One Identity Exposure version 3.93.5 contains the following bug fixes:
| Bug Fixes |
|---|
| Fixed a security issue where certain API endpoints were accessible without authentication. |
| Attack Path — Timeout and fallback for path computation When exploring all paths between two nodes in Attack Path, a three-minute time limit is now enforced. If the computation exceeds this limit, the system automatically falls back to displaying only the shortest path. This means that in environments with a large number of objects, the Attack Path view will always return a result — showing at minimum the shortest path to Tier-0 — instead of timing out with no result at all. |
| The scheduled task that launches the Indicators of Attack (IoA) event listener on Domain Controllers has been upgraded from Low priority to Normal priority. This resolves an issue where heavily loaded DCs could delay the script launch by several hours, potentially causing gaps in attack detection coverage |
| GoldenTicket Indicator of Attack (IoA) — Prevents duplicate Golden Ticket alerts when a single suspicious 4769 correlates with multiple 4624 logon events within the one-hour window. Each suspicious 4769 now raises at most one alert per profile. |
| Fixed an issue where the password reuse indicator of exposure was incorrectly raised on internal DNS partition objects (ForestDnsZones, DomainDnsZones) instead of only on the actual domain. Customers may have seen spurious password reuse deviances attributed to these non-root objects. These false positives are no longer generated. |
| IoA deployment scripts now correctly output audit policies section. |
| Fixed a bug preventing the removal of the WMI launcher (AlsidForAD-Launcher) from the DC when running IoA uninstall. |
| Fixed an issue that could prevent the read of the IoA configuration file and the start of the dedicated SMB share listener. |
| Fixed a bug preventing the Sysvol listener to restart when the Sysvol was unreachable (network) during the initial configuration. |
| Fixed health check displaying "An error as occurred" error message. |
| Tenable Identity Exposure Documentation link has been updated. |
| Indicator of Exposure (IoE) Last Password Change on KRBTGT account remediation script has been updated. |
| Megaphone icon menu button has been removed. |
| Allows the retrieval of the listenerLauncher.ps1 hash from the IoA deployment script to be able to whitelist it in the EDR prior to the IOA deployment. |
|
The Indicator of Exposure description and recommendations for Dangerous Kerberos Delegation have been restructured and expanded. Key improvements include:
|
| The error message "You can't remove the Administrator role of this user since you would lose all administration rights" is now displayed only when applicable. |
| The DYNAMIC RPC CONNECTION health check is now hidden when the Privileged Analysis toggle is disabled. |
| Escape double quotes in syslog insertion strings. |
| Fixed Compression and Removal logs tasks that failed to start due to specific folder naming formats to ensure consistent disk space management. |
| Revised the installer UI documentation's embedded hyperlinks to point to the definitive, current product documentation. |
| The timeout for getting AttackPath's paths between two nodes is now set to three minutes, and when that limit is reached, it falls back to the shortest path. |
| Addressed an issue where the Secure Relay updater scheduled task would expire and stop running after 365 days. The expiration date has been removed to ensure continuous, long-term operation. (requires SRLY update) |
| Fixed the Relay LDAP request responsible for retrieving customer Domain Controllers. The request was returning an incomplete list of Domain Controllers, which led to inaccurate IoA activity health-check status and occasional false-positive Golden Ticket alerts. |
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.93.4 | 3.93.5 |
| C++ 2015-2022 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.21.25475 | 8.0.28.26269 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 20.19.5.0 | 20.20.2.0 |
| Erlang OTP | 26.2.5.15 | 26.2.5.21 |
| Rabbit MQ | 4.0.9 | 4.0.9 |
| SQL Server | 15.0.4445.1 | 15.0.4470.1 |
| OpenSSL | 3.5 | 4.0.1 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.16.0 | 8.20.0 |
Tenable One Identity Exposure 3.77.17 (2026-04-08)
-
A decrease in installation and update times by utilizing backported MSI zip artifacts for core binaries.
Tenable One Identity Exposure version 3.77.17 contains the following bug fixes:
| Bug Fixes |
|---|
| Eliminates Golden Ticket false positives for authentication requests (4768/4770) originating locally on a Domain Controller via loopback IP. |
| Triggers an automatic re-crawl of Sysvol files if SMB network errors occur, ensuring no critical files are missed. |
| Restores RabbitMQ consumer and producer connectivity automatically following a channel shutdown. |
| Ensures the Sysvol listener reconnects properly by handling Win32Exceptions when a root directory is not found. |
| Supports successful MSI upgrades even when the Application Directory location has changed. |
| Removes orphan WMI listeners during IoA GPO uninstallation to ensure a clean environment. |
| Enables Security Profile customizations by providing necessary infrastructure data during initialization and post-login. |
| Refines the Cleanup_AdvInstServer process to exit gracefully and issue a pipeline warning if a hostname is not found. |
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.77.16 | 3.77.17 |
| C++ 2015-2019 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.23 | 8.0.25 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 20.19.5.0 | 20.20.2.0 |
| Erlang OTP | 26.2.5.16 | 26.2.5.18 |
| Rabbit MQ | 4.0.9 | 4.0.9 |
| SQL Server | 15.0.4455.2 | 15.0.4460.4 |
| OpenSSL | 3.6.1 | 3.6.1 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.18.0 | 8.19.0 |
Tenable One Identity Exposure 3.77.16 (2026-02-03)
-
Improved Indicator of Attack Filtering: All IoA detected attacks now show a unique Attack ID in a dedicated column in the IoA page.
-
Relay & Ceti monitoring: Added resource monitoring logging for on-premises deployments.
-
KRBTGT-PASSWORD Indicator of Exposure: Updated localization.
-
Attack Path computation: Improved behavior when attack paths could not be computed before timeout.
-
Attack Path edge count: Improved Edge count at startup.
Tenable One Identity Exposure version 3.77.16 contains the following bug fixes:
| Bug Fixes |
|---|
| IoA events listener persistence: Fixed persistence issue with the IoA events listener registration. |
| IoA certificate persistence: Fixed Tenable certificate persistence issue affecting Indicators of Attack. |
| Query string parsing: Fixed a regression affecting large query string arrays in API requests. |
| Software Name | Pre-upgrade | Post-upgrade |
|---|---|---|
| Tenable One Identity Exposure | 3.77.15 | 3.77.16 |
| C++ 2015-2019 Redistributable | 14.38.33135.0 | 14.38.33135.0 |
| .NET Windows Server Hosting | 8.0.22.25528 | 8.0.23 |
| IIS URL Rewrite Module 2 | 7.2.1993 | 7.2.1993 |
| Application Request Routing 3.0 | 3.0.5311 | 3.0.5311 |
| NodeJS | 20.19.5.0 | 20.19.5.0 |
| Erlang OTP | 26.2.5.16 | 26.2.5.16 |
| Rabbit MQ | 4.0.9 | 4.0.9 |
| SQL Server | 15.0.4455.2 | 15.0.4455.2 |
| OpenSSL | 3.5.1 | 3.6.1 |
| Envoy | 1.29.12 | 1.29.12 |
| Handle | 5.0 | 5.0 |
| Curl | 8.17.0 | 8.18.0 |