Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY25 SECURITY RECORDS

Tenable, Inc.

Security Center

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-19682 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19681 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19680 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19679 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19639 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19636 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19635 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19631 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19629 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19628 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-19626 14 Aug 2026 < 6.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-64881 21 Jul 2026 < 6.8.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-64880 21 Jul 2026 < 6.8.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-64879 21 Jul 2026 See the vendor and CVE records for the affected range. < 6.8.0 Update reference ↗
CVE-2026-64878 21 Jul 2026 < 6.8.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-64877 21 Jul 2026 See the vendor and CVE records for the affected range. < 6.8.0 Update reference ↗
CVE-2026-2698 23 Feb 2026 < 6.8.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2697 23 Feb 2026 < 6.8.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2630 17 Feb 2026 ≤ 6.7.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-36636 8 Oct 2025 Security Center: < 6.7.0 Tenable has released Security Center 6.7.0 to address these issues. The installation files can be obtained from the Tenable Downloads Portal: https://www.tenable.com/downloads/security-center Update reference ↗
CVE-2024-12174 9 Dec 2024 < 6.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-5759 12 Jun 2024 < 6.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1891 12 Jun 2024 < 6.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1471 14 Feb 2024 < 6.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1367 14 Feb 2024 < 6.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.