Apache Software Foundation
Apache Sling
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2023-25621 | 23 Feb 2023 | Apache Sling i18n ≤ 2.5.18 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32549 | 22 Jun 2022 | Apache Sling API ≤ 2.25.0; Apache Sling Commons Log ≤ 5.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-15717 | 10 Jan 2018 | XSS Protection API 1.0.4 to 1.0.18; XSS Protection API Compat 1.1.0; XSS Protection API 2.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2012-3353 | 8 Jan 2018 | JCR ContentLoader 2.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-15700 | 18 Dec 2017 | Authentication Service 1.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-6798 | 19 Jul 2017 | prior to 1.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-5394 | 19 Jul 2017 | prior to 1.0.12 | 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.