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

Apache Software Foundation

Apache OpenMeetings

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-49488 14 Jul 2026 5.0.0 < 9.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33005 9 Apr 2026 3.1.0 < 9.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33266 9 Apr 2026 6.1.0 < 9.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-34020 9 Apr 2026 3.1.3 < 9.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54676 8 Jan 2025 2.1 < 8.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-28936 12 May 2023 2.0.0 < 7.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-29032 12 May 2023 3.1.3 < 7.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-29246 12 May 2023 2.0.0 < 7.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-28326 28 Mar 2023 2.0.0 < 7.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-27576 15 Mar 2021 4.0.0 < Apache OpenMeetings 4*; Apache OpenMeetings 5 ≤ 5.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-1286 28 Feb 2018 3.0.0 - 4.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2016-8736 12 Oct 2017 before 3.1.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7688 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7685 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7684 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7683 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7682 14 Jul 2017 3.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7681 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7680 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7673 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7666 14 Jul 2017 1.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7664 14 Jul 2017 3.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7663 14 Jul 2017 3.2.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.