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. |
|---|---|---|---|---|---|
| Thu 30 Jul 2026· 4 changes | |||||
| 2026-07-30 | Record state changed | whole record twcert | stated at publication PUBLISHED, now states REJECTED | Time to revision 195 days | |
| 2026-07-30 | same kind of change as the line above | CVE-2026-1018 | same vendor as the line above | same change as the line above | Time to revision 195 days |
| 2026-07-30 | same kind of change as the line above | CVE-2026-1019 | same vendor as the line above | same change as the line above | Time to revision 195 days |
| 2026-07-30 | same kind of change as the line above | CVE-2026-1020 | same vendor as the line above | same change as the line above | Time to revision 195 days |
| 2026-07-30 | same kind of change as the line above | CVE-2026-1021 | same vendor as the line above | same change as the line above | Time to revision 195 days |
| Mon 1 Dec 2025· 2 changes | |||||
| 2025-12-01 | Record state changed | whole record twcert | stated at publication PUBLISHED, now states REJECTED | Time to revision 19 days | |
| 2025-12-01 | same kind of change as the line above | CVE-2025-13046 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| 2025-12-01 | same kind of change as the line above | CVE-2025-13047 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| Mon 15 Sep 2025· 1 change | |||||
| 2025-09-15 | CVSS base score changed | CVE-2025-10265 | whole record twcert | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 3 days |
| Fri 22 Aug 2025· 1 change | |||||
| 2025-08-22 | CVSS base score changed | CVE-2025-9256 | whole record twcert | stated at publication 8.7, now states 7.1CVSS v4.0 · base scoreHighHigh | Time to revision 0 days |
| Mon 21 Jul 2025· 5 changes | |||||
| 2025-07-21 | Affected range extended | CVE-2025-7916 | simopro technologywinmatrix3 twcert | stated at publication 3.8.51.1, now states 3.8.52.5Release branch starts at 0.same day | Time to revision 0 days |
| 2025-07-21 | Affected range extended | simopro technologywinmatrix3 web package twcert | stated at publication 1.2.38.1, now states 1.2.39.5Release branch starts at 0.same day | Time to revision 0 days | |
| 2025-07-21 | same kind of change as the line above | CVE-2025-7917 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-07-21 | same kind of change as the line above | CVE-2025-7918 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-07-21 | same kind of change as the line above | CVE-2025-7919 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-07-21 | same kind of change as the line above | CVE-2025-7920 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| Tue 8 Apr 2025· 1 change | |||||
| 2025-04-08 | CVSS base score changed | CVE-2025-3364 | whole record twcert | stated at publication 9.8, now states 6.7CVSS v3.1 · base scoreCriticalMedium | Time to revision 0 days |
| Fri 29 Nov 2024· 2 changes | |||||
| 2024-11-29 | Product added | CVE-2024-11981 | twcert | not named as affected at publication, now names m500 | Time to revision 0 days |
| 2024-11-29 | CVSS base score changed | CVE-2024-11980 | whole record twcert | stated at publication 10.0, now states 8.6CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Mon 4 Nov 2024· 1 change | |||||
| 2024-11-04 | CVSS base score changed | CVE-2024-10653 | whole record twcert | stated at publication 10.0, now states 7.2CVSS v3.1 · base scoreCriticalHigh | Time to revision 3 days |
| Tue 15 Oct 2024· 1 change | |||||
| 2024-10-15 | CVSS base score changed | CVE-2024-45698 | whole record twcert | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 29 days |
| Wed 14 Aug 2024· 1 change | |||||
| 2024-08-14 | Record state changed | CVE-2024-5996 | whole record twcert | stated at publication PUBLISHED, now states REJECTED | Time to revision 61 days |
| Wed 17 Jul 2024· 2 changes | |||||
| 2024-07-17 | Product added | CVE-2024-6047 | twcert | not named as affected at publication, now names gv_gm8186_vs14 and 1 more | Time to revision 30 days |
| 2024-07-17 | same kind of change as the line above | CVE-2024-6047 | same vendor as the line above | not named as affected at publication, now names gv_gm8186_vs14 | Time to revision 30 days |
| 2024-07-17 | same kind of change as the line above | CVE-2024-6047 | same vendor as the line above | not named as affected at publication, now names gv_ipcamd_gv_bx130 | Time to revision 30 days |
| Tue 18 Jun 2024· 1 change | |||||
| 2024-06-18 | Record state changed | CVE-2024-6046 | whole record twcert | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Wed 27 Mar 2024· 4 changes | |||||
| 2024-03-274 commits | CVSS base score changed | whole record twcert | stated at publication 9.8, now states 7.2CVSS v3.1 · base scoreCriticalHighBranches and original-value intervals are stated on each row. | Time to revision 202 to 250 days | |
| 2024-03-27 | same kind of change as the line above | CVE-2023-35086 | same vendor as the line above | same change as the line above | Time to revision 250 days |
| 2024-03-27 | same kind of change as the line above | CVE-2023-39239 | same vendor as the line above | same change as the line above | Time to revision 202 days |
| 2024-03-27 | same kind of change as the line above | CVE-2023-39238 | same vendor as the line above | same change as the line above | Time to revision 202 days |
| 2024-03-27 | same kind of change as the line above | CVE-2023-39240 | same vendor as the line above | same change as the line above | Time to revision 202 days |
| Wed 31 Jan 2024· 1 change | |||||
| 2024-01-31 | CVSS base score changed | CVE-2023-48387 | whole record twcert | stated at publication 6.1, now states 8.8CVSS v3.1 · base scoreMediumHigh | Time to revision 47 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 →