Hermes

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 hermes, 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-30470	18 May 2023	< da8990f737ebb9d9810633502f65ed462b819c09	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-2023-28081	18 May 2023	< e6ed9c1a4b02dc219de1648f44cd808a56171b81	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-2023-25933	18 May 2023	< e6ed9c1a4b02dc219de1648f44cd808a56171b81	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-2023-24833	18 May 2023	< a6dcafe6ded8e61658b40f5699878cd19a481f80	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-2023-24832	18 May 2023	< 5cae9f72975cf0e5a62b27fdd8b01f103e198708	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-2023-23557	18 May 2023	< a00d237346894c6067a594983be6634f4168c9ad	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-2023-23556	18 May 2023	< a6dcafe6ded8e61658b40f5699878cd19a481f80	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-40138	11 Oct 2022	unspecified < commit prior to 6aa825e480d48127b480b08d13adf70033237097	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-35289	11 Oct 2022	unspecified < prior to commit 5b6255ae049fa4641791e47fad994e8e8c4da374	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-32234	11 Oct 2022	unspecified < prior to commit 06eaec767e376bfdb883d912cb15e987ddf2bda1	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-27810	6 Oct 2022	unspecified < 0.12.0	0.12.0 < unspecified	Update reference ↗
CVE-2021-24044	15 Jan 2022	unspecified < 0.10.0	0.10.0 < unspecified	Update reference ↗
CVE-2021-24045	13 Dec 2021	unspecified < 0.10.0	0.10.0 < unspecified	Update reference ↗
CVE-2021-24037	15 Jun 2021	commit prior to d86e185e485b6330216dee8e854455c694e3a36e	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-1896	2 Feb 2021	commit prior to 86543ac47e59c522976b5632b8bf9a2a4583c7d2	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-1915	26 Oct 2020	commit prior to 8cb935cd3b2321c46aa6b7ed8454d95c75a7fca0	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-1914	8 Oct 2020	commit prior to b2021df620824627f5a8c96615edbd1eb7fdddfc	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-1913	9 Sep 2020	commit prior to 2c7af7ec481ceffd0d14ce2d7c045e475fd71dc6	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-1912	9 Sep 2020	commit prior to 091835377369c8fd5917d9b87acffa721ad2a168	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-1911	4 Sep 2020	commit prior to fe52854cdf6725c2eaa9e125995da76e6ceb27da	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.