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

elixir-ecto

postgrex

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-66838 7 Aug 2026 0.19.3 < 0.22.4; 4971a2722fa72f8e1b54a2c403cad4c43916e36d < * 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-58225 10 Jul 2026 0.16.0 < 0.22.3; 266b530faf9bde094e31e0e4ab851f933fadc0f5 < 795c6062f62c4394272ff4b89170688857b4f841 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-32687 12 May 2026 0.16.0 < 0.22.2; 266b530faf9bde094e31e0e4ab851f933fadc0f5 < 7cdedbd4316bb65f82e6a9a4f922c0ac491cb770 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.