← Search results
CVE-LINKED INVENTORY27 SECURITY RECORDS
Cure53
DOMPurify
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at dompurify, 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-75838 | 18 Aug 2026 | DOMPurify: < 3.4.13 | DOMPurify: 3.4.13 | Update reference ↗ |
| CVE-2026-66010 | 24 Jul 2026 | DOMPurify: < 3.4.12 | DOMPurify: 3.4.12 | Update reference ↗ |
| CVE-2026-65914 | 23 Jul 2026 | < 3.3.2 | 3.3.2 | Update reference ↗ |
| CVE-2026-65913 | 23 Jul 2026 | < 3.3.2 | 3.3.2 | Update reference ↗ |
| CVE-2026-65912 | 23 Jul 2026 | < 3.3.2 | 3.3.2 | Update reference ↗ |
| CVE-2026-65911 | 23 Jul 2026 | < 3.4.0 | 3.4.0 | Update reference ↗ |
| CVE-2026-65904 | 23 Jul 2026 | ≤ 3.3.3 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-65903 | 23 Jul 2026 | < 3.4.0 | 3.4.0 | Update reference ↗ |
| CVE-2026-65902 | 23 Jul 2026 | < 3.4.7 | 3.4.7 | Update reference ↗ |
| CVE-2026-65901 | 23 Jul 2026 | ≤ 3.4.6 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-65900 | 23 Jul 2026 | 3.0.0 < 3.4.8 | 3.4.8 | Update reference ↗ |
| CVE-2026-65899 | 23 Jul 2026 | < 3.4.9 | 3.4.9 | Update reference ↗ |
| CVE-2026-65898 | 23 Jul 2026 | < 3.4.11 | 3.4.11 | Update reference ↗ |
| CVE-2026-49978 | 14 Jul 2026 | < 3.4.6 | 3.4.7. | Update reference ↗ |
| CVE-2026-49459 | 14 Jul 2026 | < 3.4.6 | 3.4.6. | Update reference ↗ |
| CVE-2026-49458 | 14 Jul 2026 | < 3.4.6 | 3.4.6. | Update reference ↗ |
| CVE-2026-47423 | 14 Jul 2026 | >= 3.4.4, < 3.4.5 | 3.4.5. | Update reference ↗ |
| CVE-2026-41240 | 23 Apr 2026 | < 3.4.0 | For details on how to apply this update, refer to Ansible Automation Platform documentation. | Update reference ↗ |
| CVE-2026-41239 | 23 Apr 2026 | >= 1.0.10, < 3.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-41238 | 23 Apr 2026 | >= 3.0.1, < 3.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-0540 | 3 Mar 2026 | 3.1.3 ≤ 3.3.1; 2.5.3 ≤ 2.5.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-15599 | 3 Mar 2026 | 3.1.3 ≤ 3.2.6; 2.5.3 ≤ 2.5.8 | 3.2.7 | Update reference ↗ |
| CVE-2025-48050 | 15 May 2025 | ≤ 3.2.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-26791 | 14 Feb 2025 | < 3.2.4 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2024-48910 | 31 Oct 2024 | < 2.4.2 | If you are using an earlier version of RHACS 4.4, you are advised to upgrade to this patch release 4.4.6. | Update reference ↗ |
| CVE-2024-47875 | 11 Oct 2024 | < 2.5.0; < 3.1.3 | For OpenShift Container Platform 4.11 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.html For Red Hat OpenShift Logging 5.6, see the following instructions to apply this update: https://docs.openshift.com/container-platform/4.11/logging/cluster-logging-upgrading.html | Update reference ↗ |
| CVE-2024-45801 | 16 Sep 2024 | < 2.5.4; >=3.0.0, < 3.1.3 | Red Hat Ansible Automation Platform | 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.