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. |
|---|---|---|---|---|
| Fri 17 Jul 2026· 1 change | ||||
| 2026-07-17 | CVE-2026-7189 | whole record TR-CERT | stated at publication 8.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Fri 12 Jun 2026· 1 change | ||||
| 2026-06-12 | CVE-2026-11561 | whole record TR-CERT | stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 1 days |
| Sun 10 May 2026· 1 change | ||||
| 2026-05-10 | CVE-2026-5791 | whole record TR-CERT | stated at publication 9.6, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 3 days |
| Wed 29 Apr 2026· 1 change | ||||
| 2026-04-29 | CVE-2026-5140 | whole record TR-CERT | stated at publication 9.6, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Wed 11 Feb 2026· 1 change | ||||
| 2026-02-11 | CVE-2025-0875 | whole record TR-CERT | stated at publication 4.2, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 142 days |
| Thu 29 Jan 2026· 1 change | ||||
| 2026-01-29 | CVE-2025-7713 | whole record TR-CERT | stated at publication 8.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Tue 2 Dec 2025· 1 change | ||||
| 2025-12-02 | CVE-2025-13129 | whole record TR-CERT | stated at publication 3.5, now states 4.3CVSS v3.1 · base scoreLowMedium | Time to revision 1 days |
| Fri 3 Oct 2025· 2 changes | ||||
| 2025-10-03 | CVE-2025-10609 | whole record TR-CERT | stated at publication 7.3, now states 5.9CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| 2025-10-03 | CVE-2024-13151 | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 15 days |
| Tue 30 Sep 2025· 1 change | ||||
| 2025-09-30 | CVE-2025-8276 | whole record TR-CERT | stated at publication 10.0, now states 4.3CVSS v3.1 · base scoreCriticalMediumOriginal value first replaced 2025-09-19; this value first seen 2025-09-30. | Time to revision 3 days |
| Thu 25 Sep 2025· 1 change | ||||
| 2025-09-25 | CVE-2025-10438 | whole record TR-CERT | stated at publication 7.1, now states 8.6CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Fri 12 Sep 2025· 14 changes | ||||
| 2025-09-12 | CVE-2024-12604 | whole record TR-CERT | stated at publication 7.3, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 186 days |
| 2025-09-12 | CVE-2025-1301 | whole record TR-CERT | stated at publication 7.4, now states 6.1CVSS v3.1 · base scoreHighMedium | Time to revision 133 days |
| 2025-09-12 | CVE-2025-2421 | whole record TR-CERT | stated at publication 8.2, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 133 days |
| 2025-09-12 | CVE-2025-2488 | whole record TR-CERT | stated at publication 4.0, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 133 days |
| 2025-09-12 | CVE-2024-11142 | whole record TR-CERT | stated at publication 5.4, now states 8.8CVSS v3.1 · base scoreMediumHigh | Time to revision 133 days |
| 2025-09-12 | CVE-2024-8262 | whole record TR-CERT | stated at publication 5.5, now states 9.8CVSS v3.1 · base scoreMediumCriticalOriginal value first replaced 2025-03-10; this value first seen 2025-09-12. | Time to revision 7 days |
| 2025-09-12 | CVE-2024-7016 | whole record TR-CERT | stated at publication 7.5, now states 4.8CVSS v3.1 · base scoreHighMedium | Time to revision 295 days |
| 2025-09-122 commits | whole record TR-CERT | stated at publication 5.3, now states 7.5CVSS v3.1 · base scoreMediumHighBranches and original-value intervals are stated on each row. | Time to revision 7 to 464 days | |
| 2025-09-12 | CVE-2024-8261 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2025-03-10; this value first seen 2025-09-12. | Time to revision 7 days |
| 2025-09-12 | CVE-2024-1272 | same vendor as the line above | same change as the line above | Time to revision 464 days |
| 2025-09-12 | CVE-2023-5989 | whole record TR-CERT | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 631 days |
| 2025-09-12 | CVE-2024-1107 | whole record TR-CERT | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 442 days |
| 2025-09-12 | CVE-2024-1153 | whole record TR-CERT | stated at publication 4.3, now states 4.6CVSS v3.1 · base scoreMediumMedium | Time to revision 442 days |
| 2025-09-12 | CVE-2024-1662 | whole record TR-CERT | stated at publication 7.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 464 days |
| 2025-09-12 | CVE-2024-4341 | whole record TR-CERT | stated at publication 7.2, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 431 days |
| Tue 22 Jul 2025· 1 change | ||||
| 2025-07-22 | CVE-2025-4285 | whole record TR-CERT | stated at publication 9.8, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 days |
| Fri 13 Dec 2024· 1 change | ||||
| 2024-12-13 | CVE-2024-8259 | whole record TR-CERT | stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 4 days |
| Wed 27 Nov 2024· 1 change | ||||
| 2024-11-27 | CVE-2023-6190 | whole record TR-CERT | stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 336 days |
| Mon 25 Nov 2024· 1 change | ||||
| 2024-11-25 | CVE-2023-4671 | whole record TR-CERT | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 333 days |
| Thu 27 Jun 2024· 1 change | ||||
| 2024-06-27 | CVE-2024-0949 | whole record TR-CERT | stated at publication 4.3, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 0 days |
| Tue 5 Dec 2023· 5 changes | ||||
| 2023-12-052 commits | whole record TR-CERT | stated at publication 7.2, now states 7.5CVSS v3.1 · base scoreHighHighBranches and original-value intervals are stated on each row. | Time to revision 7 to 13 days | |
| 2023-12-05 | CVE-2023-6151 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2023-12-05 | CVE-2023-5983 | same vendor as the line above | same change as the line above | Time to revision 13 days |
| 2023-12-05 | CVE-2023-6150 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2023-12-05 | CVE-2023-6201 | whole record TR-CERT | stated at publication 9.9, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 7 days |
| 2023-12-05 | CVE-2023-4662 | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 81 days |
| Thu 30 Nov 2023· 5 changes | ||||
| 2023-11-302 commits | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCriticalBranches and original-value intervals are stated on each row. | Time to revision 0 to 49 days | |
| 2023-11-30 | CVE-2023-4972 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2023-09-14; this value first seen 2023-11-30. | Time to revision 0 days |
| 2023-11-30 | CVE-2023-5045 | same vendor as the line above | same change as the line above | Time to revision 49 days |
| 2023-11-30 | CVE-2023-5046 | same vendor as the line above | same change as the line above | Time to revision 49 days |
| 2023-11-30 | CVE-2023-4702 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2023-09-14; this value first seen 2023-11-30. | Time to revision 0 days |
| 2023-11-30 | CVE-2023-4664 | whole record TR-CERT | stated at publication 7.1, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 76 days |
| Wed 18 Oct 2023· 3 changes | ||||
| 2023-10-18 | CVE-2023-2886 | whole record TR-CERT | stated at publication 7.6, now states 4.3CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2023-07-26; this value first seen 2023-10-18. | Time to revision 62 days |
| 2023-10-18 | CVE-2023-3375 | whole record TR-CERT | stated at publication 9.1, now states 7.2CVSS v3.1 · base scoreCriticalHigh | Time to revision 43 days |
| 2023-10-18 | CVE-2023-4178 | whole record TR-CERT | stated at publication 8.2, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 43 days |
| Wed 27 Sep 2023· 1 change | ||||
| 2023-09-27 | CVE-2023-4934 | whole record TR-CERT | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Fri 15 Sep 2023· 1 change | ||||
| 2023-09-15 | CVE-2023-4661 | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 days |
| Wed 16 Aug 2023· 4 changes | ||||
| 2023-08-16 | CVE-2023-2959 | whole record TR-CERT | stated at publication 8.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 30 days |
| 2023-08-16 | CVE-2023-35067 | whole record TR-CERT | stated at publication 9.1, now states 7.5CVSS v3.1 · base scoreCriticalHigh | Time to revision 22 days |
| 2023-08-16 | CVE-2023-3632 | whole record TR-CERT | stated at publication 9.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 7 days |
| 2023-08-16 | CVE-2023-3653 | whole record TR-CERT | stated at publication 6.1, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 8 days |
| Wed 26 Jul 2023· 16 changes | ||||
| 2023-07-26 | CVE-2023-2884 | whole record TR-CERT | stated at publication 6.4, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 62 days |
| 2023-07-26 | CVE-2023-2885 | whole record TR-CERT | stated at publication 9.9, now states 8.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 62 days |
| 2023-07-26 | CVE-2023-2887 | whole record TR-CERT | stated at publication 9.1, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 62 days |
| 2023-07-262 commits | whole record TR-CERT | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCriticalBranches and original-value intervals are stated on each row. | Time to revision 9 to 67 days | |
| 2023-07-26 | CVE-2023-2958 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2023-07-26 | CVE-2023-3048 | same vendor as the line above | same change as the line above | Time to revision 43 days |
| 2023-07-26 | CVE-2023-2713 | same vendor as the line above | same change as the line above | Time to revision 67 days |
| 2023-07-26 | CVE-2023-35069 | whole record TR-CERT | stated at publication 8.6, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 13 days |
| 2023-07-262 commits | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCriticalBranches and original-value intervals are stated on each row. | Time to revision 13 to 103 days | |
| 2023-07-26 | CVE-2023-3049 | same vendor as the line above | same change as the line above | Time to revision 43 days |
| 2023-07-26 | CVE-2023-1547 | same vendor as the line above | same change as the line above | Time to revision 13 days |
| 2023-07-26 | CVE-2023-1803 | same vendor as the line above | same change as the line above | Time to revision 103 days |
| 2023-07-26 | CVE-2023-1833 | same vendor as the line above | same change as the line above | Time to revision 103 days |
| 2023-07-26 | CVE-2023-2712 | same vendor as the line above | same change as the line above | Time to revision 67 days |
| 2023-07-26 | CVE-2023-2851 | same vendor as the line above | same change as the line above | Time to revision 62 days |
| 2023-07-26 | CVE-2023-3319 | whole record TR-CERT | stated at publication 6.1, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 13 days |
| 2023-07-26 | CVE-2023-2703 | whole record TR-CERT | stated at publication 7.6, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 64 days |
| 2023-07-26 | CVE-2023-2882 | whole record TR-CERT | stated at publication 9.9, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 62 days |
| Mon 17 Apr 2023· 1 change | ||||
| 2023-04-17 | CVE-2023-1728 | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 13 days |
| Thu 6 Apr 2023· 2 changes | ||||
| 2023-04-06 | CVE-2023-1725 | whole record TR-CERT | stated at publication 8.6, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 7 days |
| 2023-04-06 | CVE-2023-1014 | whole record TR-CERT | stated at publication 5.8, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 7 days |
| Wed 5 Apr 2023· 2 changes | ||||
| 2023-04-05 | CVE-2023-0320 | whole record TR-CERT | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 16 days |
| 2023-04-05 | CVE-2023-1051 | whole record TR-CERT | stated at publication 6.5, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 13 days |
| Mon 3 Apr 2023· 1 change | ||||
| 2023-04-03 | CVE-2023-1766 | whole record TR-CERT | stated at publication 9.8, now states 6.1CVSS v3.1 · base scoreCriticalMedium | Time to revision 0 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 →