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. |
|---|---|---|---|---|
| Mon 31 Aug 2026· 1 change | ||||
| 2026-08-31 | CVE-2026-73055 | whole record VulnCheck | stated at publication 9.3, now states 6.3CVSS v4.0 · base scoreCriticalMedium | Time to revision 16 days |
| Fri 28 Aug 2026· 3 changes | ||||
| 2026-08-28 | CVE-2026-74887 | whole record VulnCheck | stated at publication 9.3, now states 6.3CVSS v4.0 · base scoreCriticalMedium | Time to revision 11 days |
| 2026-08-28 | CVE-2026-73626 | whole record VulnCheck | stated at publication 0.0, now states 7.7CVSS v4.0 · base scoreNoneHigh | Time to revision 15 days |
| 2026-08-28 | CVE-2026-80200 | whole record VulnCheck | stated at publication 0.0, now states 5.3CVSS v4.0 · base scoreNoneMedium | Time to revision 3 days |
| Wed 26 Aug 2026· 1 change | ||||
| 2026-08-26 | CVE-2026-5917 | whole record VulnCheck | stated at publication 9.6, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 15 days |
| Mon 24 Aug 2026· 13 changes | ||||
| 2026-08-24 | CVE-2026-26369 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 190 days |
| 2026-08-24 | CVE-2026-34100 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34101 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34102 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34103 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34104 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34105 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-39910 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 77 days |
| 2026-08-24 | CVE-2026-72822 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72824 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72826 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72829 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72830 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| Mon 10 Aug 2026· 1 change | ||||
| 2026-08-10 | CVE-2026-66738 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Thu 23 Jul 2026· 1 change | ||||
| 2026-07-23 | CVE-2026-63764 | whole record VulnCheck | stated at publication 9.3, now states 8.6CVSS v3.1 · base scoreCriticalHigh | Time to revision 2 days |
| Sat 18 Jul 2026· 1 change | ||||
| 2026-07-18 | CVE-2026-57857 | whole record VulnCheck | stated at publication 7.2, now states 5.1CVSS v4.0 · base scoreHighMedium | Time to revision 0 days |
| Wed 8 Jul 2026· 1 change | ||||
| 2026-07-08 | CVE-2026-60104 | whole record VulnCheck | stated at publication 8.5, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 0 days |
| Thu 2 Jul 2026· 2 changes | ||||
| 2026-07-02 | CVE-2026-56371 | whole record VulnCheck | stated at publication 0.0, now states 6.9CVSS v4.0 · base scoreNoneMedium | Time to revision 9 days |
| 2026-07-02 | CVE-2026-56379 | whole record VulnCheck | stated at publication 0.0, now states 9.2CVSS v4.0 · base scoreNoneCritical | Time to revision 9 days |
| Tue 23 Jun 2026· 1 change | ||||
| 2026-06-23 | CVE-2026-56104 | whole record VulnCheck | stated at publication 9.1, now states 8.8CVSS v4.0 · base scoreCriticalHigh | Time to revision 1 days |
| Wed 17 Jun 2026· 1 change | ||||
| 2026-06-17 | CVE-2026-55202 | whole record VulnCheck | stated at publication 9.3, now states 8.8CVSS v4.0 · base scoreCriticalHigh | Time to revision 0 days |
| Tue 26 May 2026· 1 change | ||||
| 2026-05-26 | CVE-2026-41947 | whole record VulnCheck | stated at publication 9.1, now states 9.3CVSS v4.0 · base scoreCriticalCritical | Time to revision 8 days |
| Wed 13 May 2026· 1 change | ||||
| 2026-05-13 | CVE-2026-44113 | whole record VulnCheck | stated at publication 6.0, now states 8.3CVSS v4.0 · base scoreMediumHigh | Time to revision 7 days |
| Tue 12 May 2026· 7 changes | ||||
| 2026-05-12 | CVE-2023-53878 | whole record VulnCheck | stated at publication 7.3, now states 6.9CVSS v4.0 · base scoreHighMedium | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53879 | whole record VulnCheck | stated at publication 5.3, now states 6.7CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53883 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53885 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53886 | whole record VulnCheck | stated at publication 5.7, now states 5.1CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53888 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53889 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| Thu 2 Apr 2026· 1 change | ||||
| 2026-04-02 | CVE-2023-7343 | whole record VulnCheck | stated at publication 7.8, now states 8.5CVSS v4.0 · base scoreHighHigh | Time to revision 0 days |
| Wed 25 Mar 2026· 7 changes | ||||
| 2026-03-25 | CVE-2026-22181 | whole record VulnCheck | stated at publication 6.4, now states 7.6CVSS v3.1 · base scoreMediumHigh | Time to revision 8 days |
| 2026-03-25 | CVE-2026-27183 | whole record VulnCheck | stated at publication 4.5, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 2 days |
| 2026-03-25 | CVE-2026-27524 | whole record VulnCheck | stated at publication 3.1, now states 4.3CVSS v3.1 · base scoreLowMedium | Time to revision 8 days |
| 2026-03-25 | CVE-2026-31996 | whole record VulnCheck | stated at publication 3.6, now states 4.4CVSS v3.1 · base scoreLowMedium | Time to revision 7 days |
| 2026-03-25 | CVE-2026-32000 | whole record VulnCheck | stated at publication 6.3, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 7 days |
| 2026-03-25 | CVE-2026-32019 | whole record VulnCheck | stated at publication 6.0, now states 7.4CVSS v3.1 · base scoreMediumHigh | Time to revision 6 days |
| 2026-03-25 | CVE-2026-32034 | whole record VulnCheck | stated at publication 6.8, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 6 days |
| Tue 10 Mar 2026· 1 change | ||||
| 2026-03-10 | CVE-2026-29000 | whole record VulnCheck | stated at publication 10.0, now states 9.3CVSS v4.0 · base scoreCriticalCritical | Time to revision 6 days |
| Mon 2 Mar 2026· 4 changes | ||||
| 2026-03-02 | CVE-2025-71241 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 11 days |
| 2026-03-02 | CVE-2026-26223 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 11 days |
| 2026-03-02 | CVE-2026-27474 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 11 days |
| 2026-03-02 | CVE-2026-27517 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 6 days |
| Mon 2 Feb 2026· 1 change | ||||
| 2026-02-02 | CVE-2023-54328 | whole record VulnCheck | stated at publication 9.8, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 20 days |
| Mon 26 Jan 2026· 1 change | ||||
| 2026-01-26 | CVE-2023-54337 | whole record VulnCheck | stated at publication 7.5, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 13 days |
| Thu 15 Jan 2026· 1 change | ||||
| 2026-01-15 | CVE-2026-22184 | whole record VulnCheck | stated at publication 9.3, now states 4.6CVSS v4.0 · base scoreCriticalMedium | Time to revision 8 days |
| Mon 12 Jan 2026· 1 change | ||||
| 2026-01-12 | CVE-2026-22185 | whole record VulnCheck | stated at publication 7.0, now states 4.6CVSS v4.0 · base scoreHighMediumOriginal value first replaced 2026-01-08; this value first seen 2026-01-12. | Time to revision 1 days |
| Sat 27 Dec 2025· 17 changes | ||||
| 2025-12-27 | CVE-2023-53905 | whole record VulnCheck | stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh | Time to revision 10 days |
| 2025-12-27 | CVE-2023-53930 | whole record VulnCheck | stated at publication 9.8, now states 7.5CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2025-12-27 | CVE-2023-53976 | whole record VulnCheck | stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 5 days |
| 2025-12-27 | CVE-2023-53977 | whole record VulnCheck | stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 5 days |
| 2025-12-27 | CVE-2023-53978 | whole record VulnCheck | stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 5 days |
| 2025-12-27 | CVE-2023-53918 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 10 days |
| 2025-12-27 | CVE-2023-53925 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 10 days |
| 2025-12-27 | CVE-2023-53927 | whole record VulnCheck | stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium | Time to revision 10 days |
| 2025-12-27 | CVE-2023-53931 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 10 days |
| 2025-12-27 | CVE-2023-53953 | whole record VulnCheck | stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 8 days |
| 2025-12-27 | CVE-2024-58318 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 9 days |
| 2025-12-27 | CVE-2024-58319 | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 9 days |
| 2025-12-27 | CVE-2025-2292 | whole record VulnCheck | stated at publication 4.9, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 271 days |
| 2025-12-27 | CVE-2025-2748 | whole record VulnCheck | stated at publication 6.5, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 278 days |
| 2025-12-27 | CVE-2025-30004 | whole record VulnCheck | stated at publication 9.1, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 271 days |
| 2025-12-27 | CVE-2025-30005 | whole record VulnCheck | stated at publication 6.7, now states 8.3CVSS v3.1 · base scoreMediumHigh | Time to revision 271 days |
| 2025-12-27 | CVE-2025-34509 | whole record VulnCheck | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2025-06-17; this value first seen 2025-12-27. | Time to revision 0 days |
| Thu 18 Dec 2025· 1 change | ||||
| 2025-12-18 | CVE-2023-53741 | whole record VulnCheck | stated at publication 7.1, now states 5.1CVSS v4.0 · base scoreHighMedium | Time to revision 8 days |
| Mon 15 Dec 2025· 2 changes | ||||
| 2025-12-15 | CVE-2025-34427 | whole record VulnCheck | stated at publication 6.8, now states 8.4CVSS v4.0 · base scoreMediumHigh | Time to revision 5 days |
| 2025-12-15 | CVE-2025-34428 | whole record VulnCheck | stated at publication 6.8, now states 8.4CVSS v4.0 · base scoreMediumHigh | Time to revision 5 days |
| Mon 3 Nov 2025· 1 change | ||||
| 2025-11-03 | CVE-2025-34164 | whole record VulnCheck | stated at publication 8.8, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 66 days |
| Tue 17 Jun 2025· 1 change | ||||
| 2025-06-17 | CVE-2025-34510 | whole record VulnCheck | stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Tue 8 Apr 2025· 1 change | ||||
| 2025-04-08 | CVE-2025-0942 | whole record VulnCheck | stated at publication 6.0, now states 8.6CVSS v3.1 · base scoreMediumHigh | Time to revision 1 days |
This kind is counted once per CVE record, so changes and records are the same number here.
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 →