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

http4k

http4k

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-100834 27 Sep 2026 http4k: < 6.48.0.0, < 5.42.0.0, < 4.51.0.0 http4k: 6.48.0.0, 5.42.0.0, 4.51.0.0 Update reference ↗
CVE-2026-100725 27 Sep 2026 http4k: < 6.48.0.0, < 5.42.0.0, < 4.51.0.0 http4k: 6.48.0.0, 5.42.0.0, 4.51.0.0 Update reference ↗
CVE-2026-100724 27 Sep 2026 http4k: < 6.49.0.0, < 5.42.0.0, < 4.51.0.0 http4k: 6.49.0.0, 5.42.0.0, 4.51.0.0 Update reference ↗
CVE-2026-54147 18 Sep 2026 http4k: < 4.51.0.0, >= 5.0.0.0, < 5.42.0.0, >= 6.0.0.0, < 6.50.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-54148 18 Sep 2026 http4k: < 4.51.0.0, >= 5.0.0.0, < 5.42.0.0, >= 6.0.0.0, < 6.50.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-53659 14 Sep 2026 http4k: < 4.51.0.0, >= 5.0.0.0, < 5.42.0.0, >= 6.0.0.0, < 6.49.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-55875 12 Dec 2024 < 6.50.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

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.