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

Capgo

Capgo

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 capgo, 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-56336 12 Jul 2026 Capgo: < 12.128.2 Capgo: 12.128.2 Update reference ↗
CVE-2026-56313 12 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56308 12 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56281 12 Jul 2026 Capgo: < 12.128.2 Capgo: 12.128.2 Update reference ↗
CVE-2026-56252 12 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56241 12 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56238 12 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56303 11 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56240 11 Jul 2026 < 12.128.12 12.128.12 Update reference ↗
CVE-2026-56335 10 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56329 10 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56312 10 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56309 10 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56305 10 Jul 2026 Capgo: < 12.128.2 Capgo: 12.128.2 Update reference ↗
CVE-2026-56279 10 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56298 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56293 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56283 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56250 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56246 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56220 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56217 8 Jul 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56334 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56333 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56331 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56328 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56327 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56320 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56318 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56300 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56286 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56249 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56247 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56233 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56230 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56224 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56219 30 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56338 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56337 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56302 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56257 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56256 24 Jun 2026 Capgo: < 12.128.2 Capgo: 12.128.2 Update reference ↗
CVE-2026-56244 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56237 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56232 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56231 24 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56223 24 Jun 2026 Capgo: < 12.128.2 Capgo: 12.128.2 Update reference ↗
CVE-2026-56322 23 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56243 23 Jun 2026 < 12.128.2 12.128.2 Update reference ↗
CVE-2026-56234 23 Jun 2026 < 12.128.2 12.128.2 Update reference ↗

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.