CVSS base score changed
| 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. |
|---|---|---|---|---|
| Thu 11 Dec 2025· 2 changes | ||||
| 2025-12-11 | whole record CERTVDE | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 1 days | |
| 2025-12-11 | CVE-2025-41730 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2025-12-11 | CVE-2025-41732 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Fri 21 Nov 2025· 2 changes | ||||
| 2025-11-21 | CVE-2025-25265 | whole record CERTVDE | stated at publication 7.5, now states 4.9CVSS v3.1 · base scoreHighMedium | Time to revision 158 days |
| 2025-11-21 | CVE-2025-25264 | whole record CERTVDE | stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 158 days |
| Mon 25 Aug 2025· 1 change | ||||
| 2025-08-25 | CVE-2025-41689 | whole record CERTVDE | stated at publication 5.3, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 6 days |
| Wed 23 Jul 2025· 1 change | ||||
| 2025-07-23 | CVE-2025-41663 | whole record CERTVDE | stated at publication 8.1, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 42 days |
| Wed 29 Jan 2025· 1 change | ||||
| 2025-01-29 | CVE-2024-3913 | whole record CERTVDE | stated at publication 7.5, now states 5.9CVSS v3.1 · base scoreHighMedium | Time to revision 169 days |
| Tue 1 Oct 2024· 8 changes | ||||
| 2024-10-01 | CVE-2024-41176 | whole record CERTVDE | stated at publication 6.5, now states 7.3CVSS v3.1 · base scoreMediumHigh | Time to revision 35 days |
| 2024-10-01 | whole record CERTVDE | stated at publication 6.5, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 21 days | |
| 2024-10-01 | CVE-2024-43389 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2024-10-01 | CVE-2024-43390 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2024-10-01 | CVE-2024-43391 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2024-10-01 | CVE-2024-43392 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2024-10-01 | CVE-2024-43393 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2024-10-01 | CVE-2024-6876 | whole record CERTVDE | stated at publication 5.1, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 21 days |
| 2024-10-01 | CVE-2023-46144 | whole record CERTVDE | stated at publication 7.7, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 292 days |
| Thu 15 Feb 2024· 3 changes | ||||
| 2024-02-15 | CVE-2023-50357 | whole record CERTVDE | stated at publication 4.6, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 15 days |
| 2024-02-15 | CVE-2023-6545 | whole record CERTVDE | stated at publication 4.3, now states 4.7CVSS v3.1 · base scoreMediumMedium | Time to revision 63 days |
| 2024-02-15 | CVE-2023-50356 | whole record CERTVDE | stated at publication 9.1, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 15 days |
| Thu 16 Nov 2023· 1 change | ||||
| 2023-11-16 | CVE-2023-34412 | whole record CERTVDE | stated at publication 8.3, now states 4.8CVSS v3.1 · base scoreHighMedium | Time to revision 91 days |
| Tue 14 Nov 2023· 1 change | ||||
| 2023-11-14 | CVE-2023-37858 | whole record CERTVDE | stated at publication 3.8, now states 4.9CVSS v3.1 · base scoreLowMedium | Time to revision 97 days |
| Mon 16 Oct 2023· 1 change | ||||
| 2023-10-16 | CVE-2023-4834 | whole record CERTVDE | stated at publication 6.5, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Tue 19 Sep 2023· 1 change | ||||
| 2023-09-19 | CVE-2023-3935 | whole record CERTVDE | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 6 days |
| Fri 8 Sep 2023· 1 change | ||||
| 2023-09-08 | CVE-2023-3572 | whole record CERTVDE | stated at publication 9.9, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Time to revision 31 days |
| Fri 25 Aug 2023· 5 changes | ||||
| 2023-08-25 | CVE-2023-37860 | whole record CERTVDE | stated at publication 8.6, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 16 days |
| 2023-08-25 | whole record CERTVDE | stated at publication 9.9, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 17 days | |
| 2023-08-25 | CVE-2023-3570 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2023-08-25 | CVE-2023-3571 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2023-08-25 | CVE-2023-3573 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2023-08-25 | CVE-2023-2673 | whole record CERTVDE | stated at publication 5.8, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 73 days |
This kind is counted once per CVE record, so changes and records are the same number here. 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 →