Every change, newest first
| 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. | Kind | 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. |
|---|---|---|---|---|---|
| Mon 31 Aug 2026· 11 changes | |||||
| 2026-08-313 commits | Product added | icscert | not named as affected at publication, now names ebyte na111-m firmwareBranches and original-value intervals are stated on each row. | Time to revision 0 to 4 days | |
| 2026-08-31 | same kind of change as the line above | CVE-2026-73125 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-75814 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-76179 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-76940 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-69658 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-71187 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-73809 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-75548 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 3 more rows in this change are not listed here. Open all 11 rows → | |||||
| Thu 25 Jun 2026· 2 changes | |||||
| 2026-06-25 | CVSS base score changed | CVE-2025-64308 | whole record icscert | stated at publication 8.7, now states 7.1CVSS v4.0 · base scoreHighHigh | Time to revision 223 days |
| 2026-06-25 | CVSS base score changed | CVE-2025-64309 | whole record icscert | stated at publication 8.6, now states 7.4CVSS v3.1 · base scoreHighHigh | Time to revision 223 days |
| Tue 12 May 2026· 10 changes | |||||
| 2026-05-12 | Affected range extended | CVE-2025-65084 | ashlar-vellum5 products icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65084 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65084 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65084 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65084 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65084 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65085 | ashlar-vellum5 products icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65085 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65085 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65085 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65085 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | same kind of change as the line above | CVE-2025-65085 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 168 days |
| Mon 27 Apr 2026· 49 changes | |||||
| 2026-04-272 commits | Product added | CVE-2026-28747 | icscert | not named as affected at publication, now names ms-c2964-rflpc and 48 moreBranches and original-value intervals are stated on each row. | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c2964-rflpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c2966-rflwpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c2966-x12rlpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c2966-x12rlvpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c2972-rflpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c5361-x12lpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c5366-x12lpc | Time to revision 0 days |
| 2026-04-27 | same kind of change as the line above | CVE-2026-28747 | same vendor as the line above | not named as affected at publication, now names ms-c5366-x12lvpc | Time to revision 0 days |
| 41 more rows in this change are not listed here. Open all 49 rows → | |||||
| Tue 17 Mar 2026· 1 change | |||||
| 2026-03-17 | CVSS base score changed | CVE-2025-12357 | whole record icscert | stated at publication 8.3, now states 6.3CVSS v3.1 · base scoreHighMedium | Time to revision 137 days |
| Tue 30 Dec 2025· 2 changes | |||||
| 2025-12-30 | Record state changed | whole record icscert | stated at publication PUBLISHED, now states REJECTED | Time to revision 19 days | |
| 2025-12-30 | same kind of change as the line above | CVE-2025-66584 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| 2025-12-30 | same kind of change as the line above | CVE-2025-66587 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| Wed 9 Apr 2025· 3 changes | |||||
| 2025-04-09 | Record state changed | whole record icscert | stated at publication PUBLISHED, now states REJECTED | Time to revision 265 days | |
| 2025-04-09 | same kind of change as the line above | CVE-2023-40159 | same vendor as the line above | same change as the line above | Time to revision 265 days |
| 2025-04-09 | same kind of change as the line above | CVE-2023-40223 | same vendor as the line above | same change as the line above | Time to revision 265 days |
| 2025-04-09 | same kind of change as the line above | CVE-2023-40539 | same vendor as the line above | same change as the line above | Time to revision 265 days |
| Wed 2 Apr 2025· 1 change | |||||
| 2025-04-02 | Record state changed | CVE-2024-12858 | whole record icscert | stated at publication PUBLISHED, now states REJECTED | Time to revision 20 days |
| Thu 6 Feb 2025· 1 change | |||||
| 2025-02-06 | Product added | CVE-2025-0994 | icscert | not named as affected at publication, now names cityworks (with office companion) | Time to revision 0 days |
| Thu 26 Sep 2024· 1 change | |||||
| 2024-09-26 | CVSS base score changed | CVE-2024-45374 | whole record icscert | stated at publication 5.1, now states 6.0CVSS v4.0 · base scoreMediumMedium | Time to revision 0 days |
| Thu 5 Sep 2024· 1 change | |||||
| 2024-09-05 | Product added | CVE-2024-8395 | icscert | not named as affected at publication, now names known crewmember (kcm) | Time to revision 0 days |
| Fri 7 Jul 2023· 1 change | |||||
| 2023-07-07 | CVSS base score changed | CVE-2023-35987 | whole record icscert | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 1 days |
| Wed 14 Jun 2023· 1 change | |||||
| 2023-06-14 | Product added | CVE-2023-1709 | icscert | not named as affected at publication, now names library apdfl | Time to revision 7 days |
| Mon 22 May 2023· 1 change | |||||
| 2023-05-22 | Product added | CVE-2023-28649 | icscert | not named as affected at publication, now names ovrc cloud | Time to revision 0 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →