[R1] Stand-alone Security Patch Available for Tenable Enclave Security 1.7.0 and 1.8.0: SC-202608.1

Critical

Synopsis

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

ComponentCVE ID Severity CVSS v3 BaseCVSS v3 Temporal CVSS v3 Vector
Remote Code ExecutionCVE-2026-19626Critical9.98.9AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
OS Command InjectionCVE-2026-19628High7.26.5AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
Privilege EscalationCVE-2026-19629High8.17.3AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N/E:P/RL:O/RC:C
Local Privilege EscalationCVE-2026-19635High8.87.9AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C

Note: These vulnerabilities were previously addressed in Tenable Enclave Security 1.9.0, which includes Tenable Security Center 6.9.0. 

Solution

Tenable has released Security Patch SC-202608.1 to address these issues. Additional information on installation can be obtained from the following resources:

Additional References

https://www.tenable.com/downloads/security-center
https://docs.tenable.com/release-notes/Content/enclave-security/2026.htm#190
https://developer.tenable.com/changelog/tes-new-api-documentation
https://charts.tenable.com

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]