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

LDAPAccountManager

lam

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 lam, 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-27895 17 Mar 2026 < 9.5 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-27894 17 Mar 2026 < 9.5 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-2025-58174 16 Sep 2025 < 9.3 9.3. Update reference ↗
CVE-2024-52792 17 Dec 2024 < 9.0 9.0. Update reference ↗
CVE-2024-23333 18 Mar 2024 < 8.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31085 27 Jun 2022 < 8.0 8.0. Update reference ↗
CVE-2022-31084 27 Jun 2022 < 8.0 8.0. Update reference ↗
CVE-2022-31086 27 Jun 2022 < 8.0 8.0. Update reference ↗
CVE-2022-31087 27 Jun 2022 < 8.0 8.0. Update reference ↗
CVE-2022-31088 27 Jun 2022 < 8.0 8.0. Update reference ↗
CVE-2022-24851 15 Apr 2022 < 7.9.1 7.9.1. 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.