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 6 Mar 2026· 4 changes | |||||
| 2026-03-06 | CVSS base score changed | CVE-2026-28448 | whole record VulnCheck | stated at publication 7.5, now states 7.3Assessments not comparable · base scoreHighHighOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.Not 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 |
| 2026-03-06 | CVSS base score changed | CVE-2026-28457 | whole record VulnCheck | stated at publication 7.5, now states 6.1Assessments not comparable · base scoreHighMediumOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.Not 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 |
| 2026-03-06 | CVSS base score changed | CVE-2026-28466 | whole record VulnCheck | stated at publication 9.4, now states 9.9Assessments not comparable · base scoreCriticalCriticalNot 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 1 days |
| 2026-03-06 | CVSS base score changed | CVE-2026-28467 | whole record VulnCheck | stated at publication 6.9, now states 6.5Assessments not comparable · base scoreMediumMediumNot 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 1 days |
| Thu 5 Mar 2026· 7 changes | |||||
| 2026-03-05 | CVSS base score changed | CVE-2026-28394 | whole record VulnCheck | stated at publication 7.5, now states 6.9Assessments not comparable · base scoreHighMediumNot 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 |
| 2026-03-05 | CVSS base score changed | CVE-2026-28452 | whole record VulnCheck | stated at publication 7.5, now states 6.7Assessments not comparable · base scoreHighMediumNot 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 |
| 2026-03-05 | CVSS base score changed | CVE-2026-28471 | whole record VulnCheck | stated at publication 8.4, now states 6.3Assessments not comparable · base scoreHighMediumNot 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 |
| 2026-03-05 | CVSS base score changed | CVE-2026-28475 | whole record VulnCheck | stated at publication 9.8, now states 6.3Assessments not comparable · base scoreCriticalMediumNot 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 |
| 2026-03-05 | CVSS base score changed | CVE-2026-28480 | whole record VulnCheck | stated at publication 9.8, now states 6.9Assessments not comparable · base scoreCriticalMediumNot 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 |
| 2026-03-05 | CVSS base score changed | whole record VulnCheck | stated at publication 7.5, now states 6.8Assessments not comparable · base scoreHighMediumnot counted: CVSS assessments are not comparable | Time to revision 0 days | |
| 2026-03-05 | same kind of change as the line above | CVE-2026-28486 | same vendor as the line above | same change as the line aboveNot 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 |
| 2026-03-05 | same kind of change as the line above | CVE-2026-29612 | same vendor as the line above | same change as the line aboveNot 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 |
| Wed 4 Mar 2026· 1 change | |||||
| 2026-03-04 | CVSS base score changed | CVE-2026-29022 | whole record VulnCheck | stated at publication 6.8, now states 7.3Assessments not comparable · base scoreMediumHighNot 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 1 days |
| Mon 2 Mar 2026· 5 changes | |||||
| 2026-03-02 | CVSS base score changed | CVE-2025-71242 | whole record VulnCheck | stated at publication 5.3, now states 6.5Assessments not comparable · base scoreMediumMediumNot 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 11 days |
| 2026-03-02 | CVSS base score changed | CVE-2026-26338 | whole record VulnCheck | stated at publication 6.9, now states 9.8Assessments not comparable · base scoreMediumCriticalNot 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 11 days |
| 2026-03-02 | CVSS base score changed | CVE-2026-26367 | whole record VulnCheck | stated at publication 7.1, now states 8.1Assessments 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 15 days |
| 2026-03-02 | CVSS base score changed | CVE-2026-27521 | whole record VulnCheck | stated at publication 6.9, now states 7.5Assessments not comparable · base scoreMediumHighNot 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 6 days |
| 2026-03-02 | CVSS base score changed | CVE-2026-27747 | whole record VulnCheck | stated at publication 8.7, now states 8.8Assessments not comparable · base scoreHighHighOriginal value first replaced 2026-02-25; this value first seen 2026-03-02.Not 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 1 days |
| Fri 27 Feb 2026· 4 changes | |||||
| 2026-02-27 | CVSS base score changed | CVE-2026-22206 | whole record VulnCheck | stated at publication 8.7, now states 8.8Assessments not comparable · base scoreHighHighNot 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 1 days |
| 2026-02-27 | CVSS base score changed | CVE-2026-22207 | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments 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 1 days |
| 2026-02-27 | CVSS base score changed | CVE-2026-26228 | whole record VulnCheck | stated at publication 2.3, now states 4.9Assessments not comparable · base scoreLowMediumNot 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 1 days |
| 2026-02-27 | CVSS base score changed | CVE-2026-27510 | whole record VulnCheck | stated at publication 6.4, now states 9.6Assessments 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 1 days |
| Wed 25 Feb 2026· 4 changes | |||||
| 2026-02-25 | CVSS base score changed | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalnot counted: CVSS version set changed | Time to revision 1 days | |
| 2026-02-25 | same kind of change as the line above | CVE-2026-27743 | 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 1 days |
| 2026-02-25 | same kind of change as the line above | CVE-2026-27744 | 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 1 days |
| 2026-02-25 | CVSS base score changed | CVE-2026-27745 | whole record VulnCheck | stated at publication 8.7, now states 8.8Assessments not comparable · base scoreHighHighNot 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 1 days |
| 2026-02-25 | CVSS base score changed | CVE-2026-27746 | whole record VulnCheck | stated at publication 5.1, now states 6.1Assessments not comparable · base scoreMediumMediumNot 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 1 days |
| Mon 23 Feb 2026· 1 change | |||||
| 2026-02-23 | CVSS base score changed | CVE-2026-26345 | whole record VulnCheck | stated at publication 4.7, now states 8.6Assessments not comparable · base scoreMediumHighOriginal value first replaced 2026-02-20; this value first seen 2026-02-23.Not 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 1 days |
| Fri 20 Feb 2026· 5 changes | |||||
| 2026-02-20 | CVSS base score changed | whole record VulnCheck | stated at publication 5.1, now states 6.1Assessments not comparable · base scoreMediumMediumnot counted: CVSS version set changed | Time to revision 0 days | |
| 2026-02-20 | same kind of change as the line above | CVE-2026-27502 | 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 0 days |
| 2026-02-20 | same kind of change as the line above | CVE-2026-27503 | 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 0 days |
| 2026-02-20 | same kind of change as the line above | CVE-2026-27504 | 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 0 days |
| 2026-02-20 | same kind of change as the line above | CVE-2026-27505 | 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 0 days |
| 2026-02-20 | same kind of change as the line above | CVE-2026-27506 | 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 0 days |
| Thu 19 Feb 2026· 16 changes | |||||
| 2026-02-19 | CVSS base score changed | whole record VulnCheck | stated at publication 5.1, now states 5.4Assessments not comparable · base scoreMediumMediumnot counted: CVSS version set changed | Time to revision 0 days | |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23604 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23605 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23606 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23607 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23608 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23609 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23610 | 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 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2026-23611 | 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 0 days |
| 8 more rows in this change are not listed here. Open all 16 rows → | |||||
| Tue 17 Feb 2026· 2 changes | |||||
| 2026-02-17 | CVSS base score changed | CVE-2026-22208 | whole record VulnCheck | stated at publication 9.4, now states 9.6Assessments 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 0 days |
| 2026-02-17 | CVSS base score changed | CVE-2026-23647 | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments 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 0 days |
| Wed 21 Jan 2026· 1 change | |||||
| 2026-01-21 | CVSS base score changed | CVE-2025-15113 | whole record VulnCheck | stated at publication 8.5, now states 9.3Assessments not comparable · base scoreHighCriticalNot 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 22 days |
| Fri 16 Jan 2026· 10 changes | |||||
| 2026-01-16 | CVSS base score changed | CVE-2023-53936 | whole record VulnCheck | stated at publication 5.4, now states 5.1Assessments not comparable · base scoreMediumMediumNot 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 29 days |
| 2026-01-16 | CVSS base score changed | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalnot counted: CVSS assessments are not comparable | Time to revision 17 to 25 days | |
| 2026-01-16 | same kind of change as the line above | CVE-2023-53960 | same vendor as the line above | same change as the line aboveNot 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 25 days |
| 2026-01-16 | same kind of change as the line above | CVE-2023-53983 | same vendor as the line above | same change as the line aboveNot 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 17 days |
| 2026-01-16 | same kind of change as the line above | CVE-2023-54327 | same vendor as the line above | same change as the line aboveNot 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 17 days |
| 2026-01-16 | same kind of change as the line above | CVE-2025-15111 | same vendor as the line above | same change as the line aboveNot 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 17 days |
| 2026-01-16 | CVSS base score changed | CVE-2023-53961 | whole record VulnCheck | stated at publication 5.3, now states 5.1Assessments not comparable · base scoreMediumMediumNot 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 25 days |
| 2026-01-16 | CVSS base score changed | CVE-2023-53964 | whole record VulnCheck | stated at publication 8.8, now states 9.8Assessments not comparable · base scoreHighCriticalNot 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 25 days |
| 2026-01-16 | CVSS base score changed | CVE-2024-58336 | whole record VulnCheck | stated at publication 9.8, now states 8.7Assessments not comparable · base scoreCriticalHighNot 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 17 days |
| 2026-01-16 | CVSS base score changed | CVE-2024-58338 | whole record VulnCheck | stated at publication 9.8, now states 10.0Assessments not comparable · base scoreCriticalCriticalNot 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 17 days |
| 2026-01-16 | CVSS base score changed | CVE-2025-15112 | whole record VulnCheck | stated at publication 8.0, now states 5.4Assessments not comparable · base scoreHighMediumNot 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 17 days |
| Thu 15 Jan 2026· 1 change | |||||
| 2026-01-15 | Affected range extended | CVE-2026-22200 | enhancesoftosticket VulnCheck | stated at publication 1.18.2, now states 1.18.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 3 days |
| Sat 3 Jan 2026· 1 change | |||||
| 2026-01-03 | Product added | CVE-2025-34171 | VulnCheck | not named as affected at publication, now names casaosNot 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 |
| Sat 27 Dec 2025· 14 changes | |||||
| 2025-12-27 | CVSS base score changed | whole record VulnCheck | stated at publication 5.1, now states 5.4Assessments not comparable · base scoreMediumMediumnot counted: CVSS assessments are not comparable | Time to revision 9 to 10 days | |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53736 | same vendor as the line above | same change as the line aboveNot 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 9 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53738 | same vendor as the line above | same change as the line aboveNot 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 9 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53911 | same vendor as the line above | same change as the line aboveNot 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 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53919 | same vendor as the line above | same change as the line aboveNot 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 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53920 | same vendor as the line above | same change as the line aboveNot 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 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53932 | same vendor as the line above | same change as the line aboveNot 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 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2024-58321 | same vendor as the line above | same change as the line aboveNot 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 9 days |
| 2025-12-27 | same kind of change as the line above | CVE-2024-58322 | same vendor as the line above | same change as the line aboveNot 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 9 days |
| 1 more row in this change is not listed here. Open all 9 rows → | |||||
| 2025-12-27 | CVSS base score changed | whole record VulnCheck | stated at publication 4.6, now states 5.4Assessments not comparable · base scoreMediumMediumOriginal value first replaced 2025-12-18; this value first seen 2025-12-27.not counted: CVSS assessments are not comparable | Time to revision 2 days | |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53897 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2025-12-18; this value first seen 2025-12-27.Not 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 2 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53898 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2025-12-18; this value first seen 2025-12-27.Not 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 2 days |
| 2025-12-27 | CVSS base score changed | whole record VulnCheck | stated at publication 5.4, now states 5.1Assessments not comparable · base scoreMediumMediumnot counted: CVSS assessments are not comparable | Time to revision 10 days | |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53915 | same vendor as the line above | same change as the line aboveNot 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 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53916 | same vendor as the line above | same change as the line aboveNot 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 10 days |
| 2025-12-27 | CVSS base score changed | CVE-2023-53981 | whole record VulnCheck | stated at publication 8.8, now states 8.6Assessments 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 5 days |
| Thu 18 Dec 2025· 3 changes | |||||
| 2025-12-18 | CVSS base score changed | CVE-2023-53901 | whole record VulnCheck | stated at publication 5.4, now states 7.1Assessments not comparable · base scoreMediumHighNot 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 2 days |
| 2025-12-18 | CVSS base score changed | CVE-2023-53902 | whole record VulnCheck | stated at publication 6.5, now states 7.0Assessments not comparable · base scoreMediumHighNot 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 2 days |
| 2025-12-18 | CVSS base score changed | CVE-2023-53737 | whole record VulnCheck | stated at publication 4.4, now states 5.1Assessments not comparable · base scoreMediumMediumNot 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 |
| Tue 16 Dec 2025· 1 change | |||||
| 2025-12-16 | CVSS base score changed | CVE-2025-34281 | whole record VulnCheck | stated at publication 5.1, now states 6.2Assessments not comparable · base scoreMediumMediumNot 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 60 days |
| Mon 15 Dec 2025· 3 changes | |||||
| 2025-12-15 | Affected range extended | netsupport softwaremanager VulnCheck | stated at publication 14.12.0.304, now states 14.12.0001Release branch starts at 0.not counted: Same claim, other operator | Time to revision 0 days | |
| 2025-12-15 | same kind of change as the line above | CVE-2025-34179 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2025-12-15 | same kind of change as the line above | CVE-2025-34180 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2025-12-15 | same kind of change as the line above | CVE-2025-34181 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| Fri 12 Dec 2025· 1 change | |||||
| 2025-12-12 | CVSS base score changed | CVE-2024-58304 | whole record VulnCheck | stated at publication 5.3, now states 7.5Assessments not comparable · base scoreMediumHighNot 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 1 days |
| Tue 4 Nov 2025· 3 changes | |||||
| 2025-11-04 | Affected range extended | CVE-2025-3248 | langflow-ailangflow VulnCheck | stated at publication 1.2.0, now states 1.3.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 211 days |
| 2025-11-04 | CVSS base score changed | CVE-2025-34028 | whole record VulnCheck | stated at publication 10.0, now states 9.3Assessments 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 196 days |
| 2025-11-04 | CVSS base score changed | CVE-2025-2794 | whole record VulnCheck | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot 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 218 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 →