← Search results
CVE-LINKED INVENTORY64 SECURITY RECORDS
Adobe
ColdFusion 2025
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Adobe ColdFusion 2025. 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-76002 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-75746 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-76000 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-75998 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-48273 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-76190 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-75999 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-75993 | 8 Sep 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-83961 | 3 Sep 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-71387 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48385 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-71383 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-21279 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48384 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48375 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-21269 | 11 Aug 2026 | ColdFusion 2025: ≤ 12; ColdFusion 2023: ≤ 23 | ColdFusion 2025: 13; ColdFusion 2023: 24 | Update reference ↗ |
| CVE-2026-48376 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48440 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-34635 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48386 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48362 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-71386 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-71384 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-25652 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-21273 | 11 Aug 2026 | ≤ 2025.0.11; ≤ 2023.0.22 | 2025.0.12; 2023.0.23 | Update reference ↗ |
| CVE-2026-48320 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48324 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48332 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48318 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48327 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48338 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48329 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48319 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48321 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48322 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48284 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48328 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48325 | 14 Jul 2026 | ≤ 10; ≤ 21 | 11; 22 | Update reference ↗ |
| CVE-2026-48363 | 13 Jul 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48364 | 13 Jul 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48316 | 6 Jul 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48315 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48281 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48277 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48285 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48313 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48307 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48314 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48276 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | Update reference ↗ |
| CVE-2026-48283 | 30 Jun 2026 | ≤ 9; ≤ 20 | 10; 21 | 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.