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

capstone-engine

capstone

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 capstone, 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-55893 20 Aug 2026 capstone: < 6.0.0-Alpha10 6.0.0-Alpha10. Update reference ↗
CVE-2026-55894 20 Aug 2026 capstone: < 6.0.0-Alpha10 6.0.0-Alpha10. Update reference ↗
CVE-2026-49263 14 Aug 2026 capstone: < 6.0.0-Alpha9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49282 14 Aug 2026 capstone: < 6.0.0-Alpha9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-47143 21 Jul 2026 < 5.0.8; < 6.0.0-Alpha8 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2025-68114 17 Dec 2025 <= 6.0.0-Alpha5 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2025-67873 17 Dec 2025 <= 6.0.0-Alpha5 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 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.