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

heymrun

heym

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-105396 5 Oct 2026 heym: < 0.0.112 heym: 0.0.112 Update reference ↗
CVE-2026-101050 27 Sep 2026 heym: < 0.0.53 heym: 0.0.53 Update reference ↗
CVE-2026-101049 27 Sep 2026 heym: < 0.0.53 heym: 0.0.53 Update reference ↗
CVE-2026-100865 27 Sep 2026 heym: < 0.0.53 heym: 0.0.53 Update reference ↗
CVE-2026-100864 27 Sep 2026 heym: < 0.0.91 heym: 0.0.91 Update reference ↗
CVE-2026-100863 27 Sep 2026 heym: < 0.0.91 heym: 0.0.91 Update reference ↗
CVE-2026-100862 27 Sep 2026 heym: < 0.0.91 heym: 0.0.91 Update reference ↗
CVE-2026-100861 27 Sep 2026 heym: < 0.0.105 heym: 0.0.105 Update reference ↗
CVE-2026-100860 27 Sep 2026 heym: < 0.0.105 heym: 0.0.105 Update reference ↗
CVE-2026-100859 27 Sep 2026 heym: < 0.0.106 heym: 0.0.106 Update reference ↗
CVE-2026-100858 27 Sep 2026 heym: < 0.0.109 heym: 0.0.109 Update reference ↗
CVE-2026-84207 1 Sep 2026 < 0.0.98 0.0.98 Update reference ↗
CVE-2026-45227 12 May 2026 < 0.0.21 32b7e809d987d9b018ec8daa2cdaf48f627f26f1 Update reference ↗
CVE-2026-45226 12 May 2026 < 0.0.21 3ae3ef6a7d3609da0e910f9ed6b81e99a1661ac8 Update reference ↗
CVE-2026-45225 12 May 2026 < 0.0.21 835843e6d2bf7d018cbb8e50f28f0426eaa20c84 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.