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

sparklemotion

nokogiri

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at nokogiri, 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-79772 25 Aug 2026 1.5.1 < 1.19.1 1.19.1 Update reference ↗
CVE-2026-79771 25 Aug 2026 < 1.19.3 1.19.3 Update reference ↗
CVE-2026-79770 25 Aug 2026 nokogiri: < 1.19.3 nokogiri: 1.19.3 Update reference ↗
CVE-2026-79769 25 Aug 2026 nokogiri: < 1.19.4 nokogiri: 1.19.4 Update reference ↗
CVE-2026-57438 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57437 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-57436 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-57435 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-57434 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-57235 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-57234 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57236 25 Jun 2026 < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-6494 22 Jun 2025 c29c920907366cb74af13b4dc2230e9c9e23b833 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6490 22 Jun 2025 c29c920907366cb74af13b4dc2230e9c9e23b833 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-23476 8 Dec 2022 >= 1.13.8, < 1.13.10 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-29181 20 May 2022 < 1.13.6 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-24836 11 Apr 2022 < 1.13.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-2021-41098 27 Sep 2021 < 1.12.5 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-2020-26247 30 Dec 2020 < 1.11.0.rc4 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.