Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| 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. |
|---|---|---|---|---|---|
| Fri 7 Aug 2026· 1 change | |||||
| 2026-08-07 | Product added | CVE-2025-58375 | GitHub_M | not named as affected at publication, now names frappeNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Time to revision 0 days |
| Thu 16 Apr 2026· 1 change | |||||
| 2026-04-16 | CVSS base score changed | CVE-2025-61594 | whole record GitHub_M | stated at publication 2.7, now states 2.1Assessments not comparable · base scoreLowLowNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 107 days |
| Wed 15 Apr 2026· 2 changes | |||||
| 2026-04-15 | CVSS base score changed | CVE-2026-34940 | whole record GitHub_M | stated at publication 0.0, now states 8.7Assessments not comparable · base scoreNoneHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 9 days |
| 2026-04-15 | CVSS base score changed | CVE-2026-32236 | whole record GitHub_M | stated at publication 0.0, now states 1.7Assessments not comparable · base scoreNoneLowNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 34 days |
| Thu 9 Apr 2026· 2 changes | |||||
| 2026-04-09 | CVSS base score changed | whole record GitHub_M | stated at publication 1.7, now states 8.6Assessments not comparable · base scoreLowHighnot counted: CVSS version set changed | Time to revision 65 days | |
| 2026-04-09 | same kind of change as the line above | CVE-2025-62599 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 65 days |
| 2026-04-09 | same kind of change as the line above | CVE-2025-62600 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 65 days |
| Mon 6 Apr 2026· 1 change | |||||
| 2026-04-06 | CVSS base score changed | CVE-2026-34570 | whole record GitHub_M | stated at publication 10.0, now states 8.8Assessments not comparable · base scoreCriticalHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 5 days |
| Tue 6 Jan 2026· 1 change | |||||
| 2026-01-06 | CVSS base score changed | CVE-2025-66209 | whole record GitHub_M | stated at publication 9.4, now states 10.0Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 14 days |
| Fri 26 Dec 2025· 1 change | |||||
| 2025-12-26 | CVSS base score changed | CVE-2025-64481 | whole record GitHub_M | stated at publication 0.0, now states 2.7Assessments not comparable · base scoreNoneLowNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 49 days |
| Mon 15 Dec 2025· 1 change | |||||
| 2025-12-15 | Product added | CVE-2025-64338 | GitHub_M | not named as affected at publication, now names clipbucket-v5Not counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Time to revision 0 days |
| Fri 12 Dec 2025· 1 change | |||||
| 2025-12-12 | Product added | CVE-2025-54369 | GitHub_M | not named as affected at publication, now names node-samlNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Time to revision 0 days |
| Fri 15 Nov 2024· 1 change | |||||
| 2024-11-15 | CVSS base score changed | CVE-2024-52308 | whole record GitHub_M | stated at publication 8.1, now states 8.0Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 0 days |
| Fri 11 Oct 2024· 1 change | |||||
| 2024-10-11 | CVSS base score changed | CVE-2023-39363 | whole record GitHub_M | stated at publication 5.9, now states 9.1Assessments not comparable · base scoreMediumCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 431 days |
| Tue 1 Oct 2024· 1 change | |||||
| 2024-10-01 | CVSS base score changed | CVE-2024-45613 | whole record GitHub_M | stated at publication 7.2, now states 5.1Assessments not comparable · base scoreHighMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 6 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 →