Skip to content

Product added

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

31 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Product added" published by VulnCheck, 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.
Fri 4 Sep 2026· 3 record changes
2026-09-04CVE-2026-74235VulnChecknot named as affected at publication, now names gfi clearviewDays to revision 0
2026-09-04CVE-2026-74236VulnChecknot named as affected at publication, now names gfi clearviewDays to revision 0
2026-09-04CVE-2026-74237VulnChecknot named as affected at publication, now names gfi clearviewDays to revision 0
Mon 31 Aug 2026· 1 record change
2026-08-31CVE-2026-71960VulnChecknot named as affected at publication, now names p5 v1.1Days to revision 12
Fri 14 Aug 2026· 1 record change
2026-08-14CVE-2026-73039VulnChecknot named as affected at publication, now names streamaDays to revision 1
Fri 31 Jul 2026· 1 record change
2026-07-31CVE-2026-66420VulnChecknot named as affected at publication, now names meshcentralDays to revision 1
Tue 30 Jun 2026· 1 record change
2026-06-30CVE-2026-54371VulnChecknot named as affected at publication, now names attrDays to revision 1
Thu 25 Jun 2026· 1 record change
2026-06-25CVE-2026-56115VulnChecknot named as affected at publication, now names bootimusDays to revision 2
Wed 24 Jun 2026· 1 record change
2026-06-24CVE-2026-56274VulnChecknot named as affected at publication, now names flowise componentsDays to revision 1
Tue 23 Jun 2026· 1 record change
2026-06-23CVE-2026-49494VulnChecknot named as affected at publication, now names xcitium client security (xcs)Days to revision 16
Sat 13 Jun 2026· 1 record change
2026-06-13CVE-2026-53833VulnChecknot named as affected at publication, now names openclawDays to revision 1
Thu 28 May 2026· 2 record changes
2026-05-28CVE-2026-40034VulnChecknot named as affected at publication, now names gixDays to revision 2
2026-05-28CVE-2026-40034VulnChecknot named as affected at publication, now names gix-submoduleDays to revision 2
Wed 22 Apr 2026· 3 record changes
2026-04-22CVE-2026-22191VulnChecknot named as affected at publication, now names sicuroweb (sicuro24)Days to revision 41
2026-04-22CVE-2026-22192VulnChecknot named as affected at publication, now names snmp web proDays to revision 41
2026-04-22CVE-2026-22199VulnChecknot named as affected at publication, now names snmp web proDays to revision 41
Thu 2 Apr 2026· 1 record change
2026-04-02CVE-2024-14033VulnChecknot named as affected at publication, now names hirschmann eaglesdvDays to revision 0
Tue 24 Feb 2026· 1 record change
2026-02-24CVE-2026-23693VulnChecknot named as affected at publication, now names elementskit elementor addons – advanced widgets & templates addons for elementorDays to revision 1
Thu 8 Jan 2026· 13 record changes
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dir-600Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dir-608Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dir-610Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dir-611Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dir-615Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dir-905lDays to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dns-320Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dns-325Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dns-345Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dsl-2640tDays to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dsl-500Days to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dsl-500gDays to revision 3
2026-01-08CVE-2026-0625VulnChecknot named as affected at publication, now names dsl-502gDays to revision 3

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. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

Data sources and quality

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 →

Check my CVEs against these changes →