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

Facebook

WhatsApp for Android

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-23866 1 May 2026 2.25.8.0 < 2.26.7.10; 2.25.8.0 < 2.26.15.72 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-1907 6 Oct 2020 2.20.196.16; unspecified < 2.20.196.16; 2.20.196.12; unspecified < 2.20.196.12; 2.20.90; unspecified < 2.20.90; 173.0.0.29.505; unspecified < 173.0.0.29.505 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-1906 6 Oct 2020 2.20.130; unspecified < 2.20.130; 2.20.46; unspecified < 2.20.46 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-1905 6 Oct 2020 2.20.185; unspecified < 2.20.185 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-1902 6 Oct 2020 2.20.140; unspecified < 2.20.140; 2.20.49; unspecified < 2.20.49 unspecified < 2.20.108; unspecified < 2.20.35 Update reference ↗
CVE-2020-1890 3 Sep 2020 2.20.11; unspecified < 2.20.11; 2.20.2; unspecified < 2.20.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-1886 3 Sep 2020 2.20.11; unspecified < 2.20.11; 2.20.2; unspecified < 2.20.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11931 14 Nov 2019 2.19.274; unspecified < 2.19.274; 2.19.100; unspecified < 2.19.100; unspecified ≤ 2.18.368; 2.25.3; unspecified < 2.25.3; 2.19.104 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11933 23 Oct 2019 2.19.291; unspecified < 2.19.291 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11927 27 Sep 2019 before version 2.19.143; before version 2.19.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-6350 14 Jun 2019 2.18.276; unspecified < 2.18.276; 2.18.99; unspecified < 2.18.99; 2.18.100.6; unspecified < 2.18.100.6; 2.18.100.2; unspecified < 2.18.100.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-6349 14 Jun 2019 2.18.248; unspecified < 2.18.248; 2.18.132; unspecified < 2.18.132 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-6339 14 Jun 2019 2.18.295; 2.18.180 < unspecified; 2.18.150; 2.18.103 < unspecified unspecified < 2.18.180; unspecified < 2.18.103 Update reference ↗
CVE-2019-3566 10 May 2019 2.19.104; 2.19.54 < unspecified; 2.19.52; 2.19.38; 2.19.22 < unspecified No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-6344 31 Dec 2018 2.18.293; unspecified < 2.18.293; 2.18.93; unspecified < 2.18.93; 2.18.172; unspecified < 2.18.172 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.