Rails
rails-html-sanitizer
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 rails-html-sanitizer, 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-73648 | 13 Aug 2026 | rails-html-sanitizer: >= 1.0.3, < 1.7.1 | 1.7.1. | Update reference ↗ |
| CVE-2024-53985 | 2 Dec 2024 | >= 1.6.0, < 1.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-2024-53987 | 2 Dec 2024 | >= 1.6.0, < 1.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-2024-53986 | 2 Dec 2024 | >= 1.6.0, < 1.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-2024-53988 | 2 Dec 2024 | >= 1.6.0, < 1.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-2024-53989 | 2 Dec 2024 | >= 1.6.0, < 1.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-2022-23520 | 14 Dec 2022 | < 1.4.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-23519 | 14 Dec 2022 | < 1.4.4 | 1.4.4. | Update reference ↗ |
| CVE-2022-23518 | 14 Dec 2022 | >= 1.0.3, < 1.4.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-23517 | 14 Dec 2022 | < 1.4.4 | 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-3741 | 30 Mar 2018 | <= 1.0.3 | 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 ↗ |
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.