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

hexpm

hexpm

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-86698 22 Sep 2026 hexpm: 2025-10-10 < 2026-09-22, 650faa03af511e74c1b3b49ec12d35666b6984c4 < db58cf3a86c7639708ef52ff86de0b4f938e6360 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75554 24 Aug 2026 2025-10-10 < 2026-08-24; 650faa03af511e74c1b3b49ec12d35666b6984c4 < 50cffd206490c49c92d7b63c8505949682abedb0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75542 24 Aug 2026 2025-10-18 < 2026-08-24; 71829cb6f6559bcceb1ef4e43a2fb8cdd3af654b < bf0fb9d208f0acfabf7a2f7467c8231659e322a8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-23940 13 Mar 2026 hexpm: < 2026-03-10, 82911daf5f8fb2ab44f298e3ba22b90bc1ae3746 < 495f01607d3eae4aed7ad09b2f54f31ec7a7df01 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-21622 5 Mar 2026 617e44c71f1dd9043870205f371d375c5c4d886d < bb0e42091995945deef10556f58d046a52eb7884; 2025-08-01 < 2026-03-05 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-21621 5 Mar 2026 71829cb6f6559bcceb1ef4e43a2fb8cdd3af654b < 71c127afebb7ed7cc637eb231b98feb802d62999; 2025-08-18 < 2026-03-05 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-23939 26 Feb 2026 hexpm: 931ee0ed46fa89218e0400a4f6e6d15f96406050 < 5d2ccd2f14f45a63225a73fb5b1c937baf36fdc0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-21618 19 Jan 2026 617e44c71f1dd9043870205f371d375c5c4d886d < c692438684ead90c3bcbfb9ccf4e63c768c668a8; 2025-10-01 < 2026-01-19 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. 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.