Synopsis
Security Center leverages third-party software to help provide underlying functionality. Several of the third-party components (php jwt, libssh, postgresql) were found to contain vulnerabilities, and updated versions have been made available by the providers.
Out of caution and in line with best practice, Tenable has opted to upgrade these components to address the potential impact of the issues. Security Center 6.8.0 updates php jwt to version 7.0.2, libssh to version 1.11.1 and postgresql to version 16.11 to address the identified vulnerabilities.
Additionally, several externally reported vulnerabilities were fixed:
- An Indirect Object Reference (IDOR) in Security Center allows an authenticated remote attacker to escalate privileges via the 'owner' parameter. (CVE-2026-2697)
- An improper access control vulnerability exists where an authenticated user could access areas outside of their authorized scope. (CVE-2026-2698)
Solution
Tenable has released Security Center 6.8.0 to address these issues. The installation files can be obtained from the Tenable Downloads Portal: https://www.tenable.com/downloads/security-center
Note: Patches that include fixes for Apache, PHP and Libcurl were recently released (https://www.tenable.com/security/tns-2026-06). Tenable Security Center 6.8.0 includes all of these fixes. Please refer to the Tenable SC Release Notes for more information.
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]