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

logto-io

logto

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at logto, but registry activity is not a publisher support boundary.

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-56739 24 Sep 2026 logto: < 1.43.0 1.43.0. Update reference ↗
CVE-2026-63203 24 Sep 2026 logto: >= 1.31.0, < 1.42.0 1.42.0. Update reference ↗
CVE-2026-82263 28 Aug 2026 logto: ≤ 1.42.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-82262 28 Aug 2026 logto: ≤ 1.42.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-63187 19 Aug 2026 >= 1.40.1, < 1.41.0 1.41.0. Update reference ↗
CVE-2026-63188 19 Aug 2026 < 0.3.9 0.3.9. Update reference ↗
CVE-2026-62317 19 Aug 2026 < 1.41.0 1.41.0. Update reference ↗
CVE-2026-55377 10 Jul 2026 < 1.41.0 1.41.0. Update reference ↗
CVE-2026-55370 10 Jul 2026 < 1.41.0 1.41.0. Update reference ↗
CVE-2026-55789 10 Jul 2026 < 1.41.0 1.41.0. Update reference ↗
CVE-2026-54714 10 Jul 2026 < 1.41.0 1.41.0. 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.