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

Atlassian

Confluence

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 CVE identity is linked to the Lifecycle record Confluence. Use that record for publisher support phases and retirement dates.

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-2022-26138 20 Jul 2022 Questions For Confluence: 2.7.34, 2.7.35, 3.0.2 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-2018-13389 10 Jul 2018 unspecified < 6.6.1 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-2017-18085 2 Feb 2018 prior to 6.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-18084 2 Feb 2018 prior to 6.3.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-18083 2 Feb 2018 prior to 6.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-16856 5 Dec 2017 All versions prior to version 6.5.2 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.