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

TeamViewer

DEX

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

Lifecycle evidence status

Official registry publication history is available at dex, but registry activity is not a publisher support boundary.

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-23570 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23569 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23568 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23567 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23566 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23565 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23564 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23571 29 Jan 2026 ≤ 20 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23563 29 Jan 2026 < 26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64995 11 Dec 2025 < 3.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64994 11 Dec 2025 < 17.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64993 11 Dec 2025 < 29; < 30 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64992 11 Dec 2025 < 25 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64991 11 Dec 2025 < 15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64990 11 Dec 2025 < 21.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64989 11 Dec 2025 < 21.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64988 11 Dec 2025 < 19.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64987 11 Dec 2025 ≤ 21 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64986 11 Dec 2025 < 21 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-46266 11 Dec 2025 < 25.11.0.29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-44016 11 Dec 2025 < 25.11.0.29; ≤ 25.9.0.46; ≤ 25.5.0.53; ≤ 24.5.0.69 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-12687 11 Dec 2025 < 25.11.0.29; ≤ 25.9.0.46; ≤ 25.5.053; ≤ 24.5.0.69 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.