Skip to content

Product added

What a record said when it was published, what it says now, and the commit that changed it.

34 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Product added" published by GitHub_M, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Thu 13 Aug 2026· 1 change
2026-08-13CVE-2026-73666GitHub_Mnot named as affected at publication, now names backstage-pluginsTime to revision 0 days
Tue 4 Aug 2026· 1 change
2026-08-04CVE-2026-40181GitHub_Mnot named as affected at publication, now names @remix-run/routerTime to revision 63 days
Tue 2 Jun 2026· 1 change
2026-06-02CVE-2026-22029GitHub_Mnot named as affected at publication, now names @remix-run/routerTime to revision 144 days
Wed 20 May 2026· 1 change
2026-05-20CVE-2024-49767GitHub_Mnot named as affected at publication, now names quartTime to revision 572 days
Wed 22 Apr 2026· 1 change
2026-04-22CVE-2026-33471GitHub_Mnot named as affected at publication, now names nimiq-blockTime to revision 0 days
Mon 30 Mar 2026· 1 change
2026-03-30CVE-2026-33634GitHub_Mnot named as affected at publication, now names telnyxTime to revision 7 days
Wed 25 Mar 2026· 1 change
2026-03-25CVE-2026-33634GitHub_Mnot named as affected at publication, now names litellmTime to revision 2 days
Mon 23 Mar 2026· 4 changes
2026-03-23CVE-2026-33167GitHub_Mnot named as affected at publication, now names actionpackTime to revision 0 days
2026-03-23CVE-2026-33168GitHub_Mnot named as affected at publication, now names actionviewTime to revision 0 days
2026-03-23CVE-2026-33169GitHub_Mnot named as affected at publication, now names activesupportTime to revision 0 days
2026-03-23CVE-2026-33170GitHub_Mnot named as affected at publication, now names activesupportTime to revision 0 days
Fri 13 Feb 2026· 16 changes
2026-02-13CVE-2025-61678GitHub_Mnot named as affected at publication, now names endpointmanTime to revision 122 days
2026-02-13CVE-2025-62173GitHub_Mnot named as affected at publication, now names restappsTime to revision 72 days
2026-02-13CVE-2025-64328GitHub_Mnot named as affected at publication, now names filestoreTime to revision 99 days
2026-02-13CVE-2025-66039GitHub_Mnot named as affected at publication, now names frameworkTime to revision 66 days
2026-02-13CVE-2025-67513GitHub_Mnot named as affected at publication, now names endpointTime to revision 65 days
2026-02-13CVE-2025-67722GitHub_Mnot named as affected at publication, now names frameworkTime to revision 60 days
2026-02-13CVE-2025-67736GitHub_Mnot named as affected at publication, now names ttsTime to revision 60 days
2026-02-13CVE-2025-55209GitHub_Mnot named as affected at publication, now names contactmanagerTime to revision 162 days
2026-02-13CVE-2025-55211GitHub_Mnot named as affected at publication, now names frameworkTime to revision 151 days
2026-02-13CVE-2025-55739GitHub_Mnot named as affected at publication, now names apiTime to revision 162 days
2026-02-13CVE-2025-57819GitHub_Mnot named as affected at publication, now names endpointTime to revision 169 days
2026-02-13CVE-2025-59051GitHub_Mnot named as affected at publication, now names endpointTime to revision 122 days
2026-02-13CVE-2025-59056GitHub_Mnot named as affected at publication, now names frameworkTime to revision 151 days
2026-02-13CVE-2025-59429GitHub_Mnot named as affected at publication, now names coreTime to revision 122 days
2026-02-13CVE-2025-61675GitHub_Mnot named as affected at publication, now names endpointTime to revision 122 days
2026-02-13CVE-2024-47071GitHub_Mnot named as affected at publication, now names endpointmanTime to revision 500 days
Thu 12 Feb 2026· 1 change
2026-02-12CVE-2026-26185GitHub_Mnot named as affected at publication, now names @directus/apiTime to revision 0 days
Wed 3 Jul 2024· 1 change
2024-07-03CVE-2024-38519GitHub_Mnot named as affected at publication, now names youtube-dlTime to revision 1 days
Sat 17 Feb 2024· 2 changes
2024-02-17CVE-2024-24762GitHub_Mnot named as affected at publication, now names starletteTime to revision 12 days
2024-02-17CVE-2024-24762GitHub_Mnot named as affected at publication, now names python-multipartTime to revision 12 days
Fri 15 Sep 2023· 1 change
2023-09-15CVE-2023-37905GitHub_Mnot named as affected at publication, now names cms-rte-ckeditorTime to revision 56 days
Wed 17 May 2023· 1 change
2023-05-17CVE-2023-27482GitHub_Mnot named as affected at publication, now names supervisorTime to revision 71 days
Wed 10 May 2023· 1 change
2023-05-10CVE-2023-25568GitHub_Mnot named as affected at publication, now names boxoTime to revision 1 days

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →