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 3 Jul 2026· 1 change | ||||
| 2026-07-03 | CVE-2026-12823 | VulDB | not named as affected at publication, now names skills | Time to revision 11 days |
| Mon 2 Feb 2026· 1 change | ||||
| 2026-02-02 | CVE-2026-1743 | VulDB | not named as affected at publication, now names air | Time to revision 0 days |
| Sat 13 Sep 2025· 1 change | ||||
| 2025-09-13 | CVE-2025-9135 | VulDB | not named as affected at publication, now names salzburg verkehr | Time to revision 25 days |
| Tue 2 Sep 2025· 2 changes | ||||
| 2025-09-02 | CVE-2025-5078 | VulDB | not named as affected at publication, now names online shopping portal | Time to revision 103 days |
| 2025-09-02 | CVE-2025-5079 | VulDB | not named as affected at publication, now names online shopping portal | Time to revision 103 days |
| Mon 1 Sep 2025· 4 changes | ||||
| 2025-09-01 | CVE-2024-7218 | VulDB | not named as affected at publication, now names school log management system | Time to revision 398 days |
| 2025-09-01 | CVE-2024-7219 | VulDB | not named as affected at publication, now names school log management system | Time to revision 398 days |
| 2025-09-01 | CVE-2024-7220 | VulDB | not named as affected at publication, now names school log management system | Time to revision 398 days |
| 2025-09-01 | CVE-2024-7221 | VulDB | not named as affected at publication, now names school log management system | Time to revision 398 days |
| Mon 25 Aug 2025· 1 change | ||||
| 2025-08-25 | CVE-2025-9236 | VulDB | not named as affected at publication, now names i-educar | Time to revision 5 days |
| Tue 15 Jul 2025· 1 change | ||||
| 2025-07-15 | CVE-2025-6151 | VulDB | not named as affected at publication, now names tl-wr841n v11 | Time to revision 29 days |
| Fri 30 May 2025· 3 changes | ||||
| 2025-05-30 | CVE-2025-4226 | VulDB | not named as affected at publication, now names cyber cafe management system | Time to revision 27 days |
| 2025-05-30 | CVE-2025-4696 | VulDB | not named as affected at publication, now names cyber cafe management system | Time to revision 15 days |
| 2025-05-30 | CVE-2025-4695 | VulDB | not named as affected at publication, now names cyber cafe management system | Time to revision 15 days |
| Sun 18 May 2025· 1 change | ||||
| 2025-05-18 | CVE-2024-12950 | VulDB | not named as affected at publication, now names travel management system | Time to revision 143 days |
| Fri 16 May 2025· 1 change | ||||
| 2025-05-16 | CVE-2025-1578 | VulDB | not named as affected at publication, now names online shopping portal | Time to revision 83 days |
| Wed 30 Apr 2025· 1 change | ||||
| 2025-04-30 | CVE-2024-2777 | VulDB | not named as affected at publication, now names online marriage registration system | Time to revision 405 days |
| Thu 3 Apr 2025· 1 change | ||||
| 2025-04-03 | CVE-2023-1030 | VulDB | not named as affected at publication, now names online boat reservation system | Time to revision 769 days |
| Thu 13 Mar 2025· 1 change | ||||
| 2025-03-13 | CVE-2025-1354 | VulDB | not named as affected at publication, now names rt-n10e | Time to revision 25 days |
| Tue 4 Mar 2025· 1 change | ||||
| 2025-03-04 | CVE-2023-3694 | VulDB | not named as affected at publication, now names house rental and property listing | Time to revision 597 days |
| Sun 28 Jul 2024· 1 change | ||||
| 2024-07-28 | CVE-2024-3768 | VulDB | not named as affected at publication, now names news portal | Time to revision 104 days |
| Tue 16 Apr 2024· 1 change | ||||
| 2024-04-16 | CVE-2024-3764 | VulDB | not named as affected at publication, now names sdk | Time to revision 1 days |
| Tue 9 Jan 2024· 78 changes | ||||
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e400 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e450 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e550 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names trio 8300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 101 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 150 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 201 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 250 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 301 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 310 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 311 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 400 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 401 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 410 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 411 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 450 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 501 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 600 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 601 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e400 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e450 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e550 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names trio 8300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 101 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 150 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 201 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 250 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 301 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 310 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 311 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 400 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 401 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 410 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 411 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 450 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 501 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 600 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 601 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e400 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e450 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e500 | Time to revision 11 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.
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 →