[R1] Tenable Identity Exposure Versions 3.93.6 and 3.77.18 Fix Multiple Vulnerabilities

Critical

Synopsis

Several vulnerabilities have been identified, reported to Tenable and resolved. Please see the full list of resolved issues below.

  • A command injection vulnerability in the Active Directory Events Listener of Tenable Identity Exposure allows an authenticated, low-privileged attacker to execute arbitrary commands as SYSTEM on the PDCe - CVE-2026-119314
  • A denial-of-service vulnerability exists in the Tenable Identity Exposure GraphQL API. An authenticated, low-privileged user can submit specially crafted queries that consume excessive server resources, potentially degrading or denying service to legitimate users - CVE-2026-119315
  • An information disclosure vulnerability exists in the Tenable Identity Exposure Windows Secure Relay. A failed Secure Relay installation writes the linking key to the local error log, where a user with access to the host could read it - CVE-2026-119316

Solution

Tenable has released Tenable Identity Exposure versions 3.93.6 and 3.77.18 to address these issues. The installation files can be obtained from the Tenable Downloads Portal: https://www.tenable.com/downloads/identity-exposure

This page contains information regarding security vulnerabilities that may impact Tenable's products. This may include issues specific to our software, or due to the use of third-party libraries within our software. Tenable strongly encourages users to ensure that they upgrade or apply relevant patches in a timely manner.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]