sunnyadn
js-toml
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 js-toml, 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-63386 | 22 Sep 2026 | js-toml: < 1.1.3 | 1.1.3. | Update reference ↗ |
| CVE-2026-50029 | 14 Aug 2026 | js-toml: < 1.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-49293 | 19 Jun 2026 | < 1.1.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-2025-54803 | 5 Aug 2025 | < 1.0.2 | 1.0.2. | 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.