acacode
swagger-typescript-api
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 swagger-typescript-api, 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-54666 | 29 Jul 2026 | < 13.12.2 | 13.12.2. | Update reference ↗ |
| CVE-2026-54664 | 29 Jul 2026 | < 13.12.2 | 13.12.2. | Update reference ↗ |
| CVE-2026-54661 | 29 Jul 2026 | < 13.12.2 | 13.12.2. | Update reference ↗ |
| CVE-2026-54663 | 29 Jul 2026 | < 13.12.2 | 13.12.2. | Update reference ↗ |
| CVE-2026-54662 | 29 Jul 2026 | < 13.12.2 | 13.12.2. | Update reference ↗ |
| CVE-2026-54660 | 29 Jul 2026 | < 13.12.2 | 13.12.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.