Publisher not identified
safe-eval
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 safe-eval, 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-2023-26122 | 11 Apr 2023 | < * | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-26121 | 11 Apr 2023 | < * | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-25904 | 21 Dec 2022 | < unspecified | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-7710 | 21 Aug 2020 | < unspecified | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.