Product added
| 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 changed | Days 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-04 | CVE-2026-74235 | VulnCheck | not named as affected at publication, now names gfi clearview | Days to revision 0 |
| 2026-09-04 | CVE-2026-74236 | VulnCheck | not named as affected at publication, now names gfi clearview | Days to revision 0 |
| 2026-09-04 | CVE-2026-74237 | VulnCheck | not named as affected at publication, now names gfi clearview | Days to revision 0 |
| Mon 31 Aug 2026· 1 record change | ||||
| 2026-08-31 | CVE-2026-71960 | VulnCheck | not named as affected at publication, now names p5 v1.1 | Days to revision 12 |
| Fri 14 Aug 2026· 1 record change | ||||
| 2026-08-14 | CVE-2026-73039 | VulnCheck | not named as affected at publication, now names streama | Days to revision 1 |
| Fri 31 Jul 2026· 1 record change | ||||
| 2026-07-31 | CVE-2026-66420 | VulnCheck | not named as affected at publication, now names meshcentral | Days to revision 1 |
| Tue 30 Jun 2026· 1 record change | ||||
| 2026-06-30 | CVE-2026-54371 | VulnCheck | not named as affected at publication, now names attr | Days to revision 1 |
| Thu 25 Jun 2026· 1 record change | ||||
| 2026-06-25 | CVE-2026-56115 | VulnCheck | not named as affected at publication, now names bootimus | Days to revision 2 |
| Wed 24 Jun 2026· 1 record change | ||||
| 2026-06-24 | CVE-2026-56274 | VulnCheck | not named as affected at publication, now names flowise components | Days to revision 1 |
| Tue 23 Jun 2026· 1 record change | ||||
| 2026-06-23 | CVE-2026-49494 | VulnCheck | not named as affected at publication, now names xcitium client security (xcs) | Days to revision 16 |
| Sat 13 Jun 2026· 1 record change | ||||
| 2026-06-13 | CVE-2026-53833 | VulnCheck | not named as affected at publication, now names openclaw | Days to revision 1 |
| Thu 28 May 2026· 2 record changes | ||||
| 2026-05-28 | CVE-2026-40034 | VulnCheck | not named as affected at publication, now names gix | Days to revision 2 |
| 2026-05-28 | CVE-2026-40034 | VulnCheck | not named as affected at publication, now names gix-submodule | Days to revision 2 |
| Wed 22 Apr 2026· 3 record changes | ||||
| 2026-04-22 | CVE-2026-22191 | VulnCheck | not named as affected at publication, now names sicuroweb (sicuro24) | Days to revision 41 |
| 2026-04-22 | CVE-2026-22192 | VulnCheck | not named as affected at publication, now names snmp web pro | Days to revision 41 |
| 2026-04-22 | CVE-2026-22199 | VulnCheck | not named as affected at publication, now names snmp web pro | Days to revision 41 |
| Thu 2 Apr 2026· 1 record change | ||||
| 2026-04-02 | CVE-2024-14033 | VulnCheck | not named as affected at publication, now names hirschmann eaglesdv | Days to revision 0 |
| Tue 24 Feb 2026· 1 record change | ||||
| 2026-02-24 | CVE-2026-23693 | VulnCheck | not named as affected at publication, now names elementskit elementor addons – advanced widgets & templates addons for elementor | Days to revision 1 |
| Thu 8 Jan 2026· 13 record changes | ||||
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-600 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-608 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-610 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-611 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-615 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-905l | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dns-320 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dns-325 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dns-345 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-2640t | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-500 | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-500g | Days to revision 3 |
| 2026-01-08 | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-502g | Days 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.
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 →