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

MessagePack-CSharp

MessagePack-CSharp

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-48109 22 Jun 2026 >= 3.1.7, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48502 22 Jun 2026 >= 3.1.7, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48506 22 Jun 2026 >= 3.1.7, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48509 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48510 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48511 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48512 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48513 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48514 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48515 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48516 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-48517 22 Jun 2026 >= 3.0, < 3.1.7; < 2.5.301 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-48924 17 Oct 2024 < 2.5.187; >= 2.6.95-alpha, < 3.0.214-rc.1 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.