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. |
|---|---|---|---|---|
| Tue 1 Sep 2026· 1 change | ||||
| 2026-09-01 | CVE-2026-6876 | whole record SN | stated at publication 8.7, now states 10.0CVSS v4.0 · base scoreHighCritical | Time to revision 5 days |
| Thu 27 Aug 2026· 1 change | ||||
| 2026-08-27 | CVE-2026-59354 | whole record vmware | stated at publication 6.1, now states 9.6CVSS v3.1 · base scoreMediumCritical | Time to revision 0 days |
| Thu 20 Aug 2026· 2 changes | ||||
| 2026-08-20 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 37 days | |
| 2026-08-20 | CVE-2026-54117 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| 2026-08-20 | CVE-2026-54118 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| Wed 5 Aug 2026· 2 changes | ||||
| 2026-08-05 | CVE-2026-71213 | whole record TuranSec | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71256 | whole record TuranSec | stated at publication 8.1, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Mon 13 Jul 2026· 1 change | ||||
| 2026-07-13 | CVE-2026-12257 | whole record INCIBE | stated at publication 5.1, now states 9.3CVSS v4.0 · base scoreMediumCritical | Time to revision 0 days |
| Wed 8 Jul 2026· 2 changes | ||||
| 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 |
| 2026-07-08 | CVE-2026-9182 | whole record Esri | stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 2 days |
| Thu 2 Jul 2026· 2 changes | ||||
| 2026-07-02 | CVE-2026-56004 | whole record suse | stated at publication 8.8, now states 10.0CVSS v3.1 · base scoreHighCritical | Time to revision 0 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-12628 | whole record ibm | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 1 days |
| Fri 12 Jun 2026· 2 changes | ||||
| 2026-06-12 | CVE-2026-11535 | whole record Vivo | stated at publication 8.7, now states 9.4CVSS v4.0 · base scoreHighCritical | Time to revision 0 days |
| 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 |
| Thu 4 Jun 2026· 1 change | ||||
| 2026-06-04 | CVE-2025-71316 | whole record cisa-cg | stated at publication 7.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Wed 3 Jun 2026· 1 change | ||||
| 2026-06-03 | CVE-2026-4480 | whole record redhat | stated at publication 8.5, now states 9.0CVSS v3.1 · base scoreHighCritical | Time to revision 8 days |
| Thu 23 Apr 2026· 7 changes | ||||
| 2026-04-23 | whole record Patchstack | stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCriticalBranches and original-value intervals are stated on each row. | Time to revision 224 to 246 days | |
| 2026-04-23 | CVE-2025-49400 | same vendor as the line above | same change as the line above | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49422 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49408 | whole record Patchstack | stated at publication 4.9, now states 10.0CVSS v3.1 · base scoreMediumCritical | Time to revision 246 days |
| 2026-04-23 | whole record Patchstack | stated at publication 5.9, now states 9.8CVSS v3.1 · base scoreMediumCriticalBranches and original-value intervals are stated on each row. | Time to revision 224 to 246 days | |
| 2026-04-23 | CVE-2025-49409 | same vendor as the line above | same change as the line above | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49434 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49890 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49410 | whole record Patchstack | stated at publication 6.5, now states 10.0CVSS v3.1 · base scoreMediumCritical | Time to revision 246 days |
| Wed 8 Apr 2026· 1 change | ||||
| 2026-04-08 | CVE-2023-6972 | whole record Wordfence | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 838 days |
| Wed 1 Apr 2026· 1 change | ||||
| 2026-04-01 | CVE-2026-20963 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 78 days |
| Mon 23 Mar 2026· 1 change | ||||
| 2026-03-23 | CVE-2026-26137 | whole record microsoft | stated at publication 8.9, now states 9.9CVSS v3.1 · base scoreHighCritical | Time to revision 4 days |
| Tue 3 Mar 2026· 1 change | ||||
| 2026-03-03 | CVE-2025-37184 | whole record hpe | stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 48 days |
| Thu 29 Jan 2026· 1 change | ||||
| 2026-01-29 | CVE-2024-4447 | whole record dotCMS | stated at publication 4.9, now states 9.9CVSS v3.1 · base scoreMediumCritical | Time to revision 552 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 |
| Tue 20 Jan 2026· 1 change | ||||
| 2026-01-20 | CVE-2026-23947 | whole record GitHub_M | stated at publication 8.9, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 1 days |
| Mon 12 Jan 2026· 1 change | ||||
| 2026-01-12 | CVE-2023-34976 | whole record qnap | stated at publication 4.3, now states 10.0CVSS v3.1 · base scoreMediumCritical | Time to revision 822 days |
| Tue 16 Dec 2025· 1 change | ||||
| 2025-12-16 | CVE-2025-61811 | whole record adobe | stated at publication 8.4, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 7 days |
| 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 |
| Sat 22 Nov 2025· 3 changes | ||||
| 2025-11-22 | whole record microsoft | stated at publication 6.5, now states 9.3CVSS v3.1 · base scoreMediumCritical | Time to revision 43 days | |
| 2025-11-22 | CVE-2025-59252 | same vendor as the line above | same change as the line above | Time to revision 43 days |
| 2025-11-22 | CVE-2025-59272 | same vendor as the line above | same change as the line above | Time to revision 43 days |
| 2025-11-22 | CVE-2025-59286 | same vendor as the line above | same change as the line above | Time to revision 43 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 |
| Thu 23 Oct 2025· 1 change | ||||
| 2025-10-23 | CVE-2025-55321 | whole record microsoft | stated at publication 8.7, now states 9.3CVSS v3.1 · base scoreHighCritical | Time to revision 14 days |
| Wed 8 Oct 2025· 1 change | ||||
| 2025-10-08 | CVE-2025-6763 | whole record VulDB | stated at publication 7.7, now states 9.2CVSS v4.0 · base scoreHighCritical | Time to revision 103 days |
| Fri 12 Sep 2025· 3 changes | ||||
| 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-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-1107 | whole record TR-CERT | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 442 days |
| Thu 11 Sep 2025· 2 changes | ||||
| 2025-09-11 | CVE-2025-8311 | whole record dotCMS | stated at publication 5.5, now states 9.4CVSS v4.0 · base scoreMediumCritical | Time to revision 7 days |
| 2025-09-11 | CVE-2025-41375 | whole record INCIBE | stated at publication 8.7, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 41 days |
| Thu 4 Sep 2025· 1 change | ||||
| 2025-09-04 | CVE-2025-7679 | whole record ABB | stated at publication 8.9, now states 9.2CVSS v4.0 · base scoreHighCritical | Time to revision 23 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 |
| Mon 7 Jul 2025· 1 change | ||||
| 2025-07-07 | CVE-2025-30012 | whole record sap | stated at publication 3.9, now states 10.0CVSS v3.1 · base scoreLowCritical | Time to revision 56 days |
| Fri 13 Jun 2025· 1 change | ||||
| 2025-06-13 | CVE-2025-3623 | whole record Wordfence | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 31 days |
| Wed 7 May 2025· 1 change | ||||
| 2025-05-07 | CVE-2025-46572 | whole record GitHub_M | stated at publication 8.2, now states 9.3CVSS v4.0 · base scoreHighCriticalOriginal value first replaced 2025-05-06; this value first seen 2025-05-07. | Time to revision 0 days |
| Fri 4 Apr 2025· 2 changes | ||||
| 2025-04-04 | CVE-2025-23215 | whole record GitHub_M | stated at publication 0.0, now states 9.3CVSS v4.0 · base scoreNoneCritical | Time to revision 63 days |
| 2025-04-04 | CVE-2024-11235 | whole record php | stated at publication 7.5, now states 9.2CVSS v4.0 · base scoreHighCritical | Time to revision 0 days |
| Fri 28 Mar 2025· 1 change | ||||
| 2025-03-28 | CVE-2025-24383 | whole record dell | stated at publication 7.8, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Thu 20 Mar 2025· 2 changes | ||||
| 2025-03-20 | whole record GitHub_M | stated at publication 8.0, now states 9.3CVSS v4.0 · base scoreHighCriticalOriginal value first replaced 2025-03-12; this value first seen 2025-03-20. | Time to revision 0 days | |
| 2025-03-20 | CVE-2025-25291 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2025-03-12; this value first seen 2025-03-20. | Time to revision 0 days |
| 2025-03-20 | CVE-2025-25292 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2025-03-12; this value first seen 2025-03-20. | Time to revision 0 days |
| Thu 16 Jan 2025· 1 change | ||||
| 2025-01-16 | CVE-2024-54034 | whole record adobe | stated at publication 8.0, now states 9.3CVSS v3.1 · base scoreHighCritical | Time to revision 37 days |
| Tue 14 Jan 2025· 1 change | ||||
| 2025-01-14 | CVE-2024-54036 | whole record adobe | stated at publication 8.2, now states 9.3CVSS v3.1 · base scoreHighCritical | Time to revision 35 days |
| Tue 31 Dec 2024· 1 change | ||||
| 2024-12-31 | CVE-2024-38183 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 105 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 |
| Fri 8 Nov 2024· 1 change | ||||
| 2024-11-08 | CVE-2024-51501 | whole record GitHub_M | stated at publication 2.3, now states 10.0CVSS v4.0 · base scoreLowCritical | Time to revision 4 days |
| Tue 15 Oct 2024· 1 change | ||||
| 2024-10-15 | CVE-2024-45698 | whole record twcert | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 29 days |
| Wed 4 Sep 2024· 5 changes | ||||
| 2024-09-04 | CVE-2024-7923 | whole record redhat | stated at publication 4.2, now states 9.8CVSS v3.0 · base scoreMediumCritical | Time to revision 0 days |
| 2024-09-04 | CVE-2024-8181 | whole record tenable | stated at publication 7.3, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 8 days |
| 2024-09-042 commits | whole record CERT-In | stated at publication 7.5, now states 9.1CVSS v4.0 · base scoreHighCriticalBranches and original-value intervals are stated on each row. | Time to revision 1 days | |
| 2024-09-04 | CVE-2024-45588 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2024-09-04 | CVE-2024-45587 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2024-09-04 | CVE-2024-45586 | whole record CERT-In | stated at publication 7.5, now states 9.2CVSS v4.0 · base scoreHighCritical | Time to revision 1 days |
| Wed 7 Aug 2024· 1 change | ||||
| 2024-08-07 | CVE-2024-35198 | whole record GitHub_M | stated at publication 5.7, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 20 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 |
| Wed 26 Jun 2024· 1 change | ||||
| 2024-06-26 | CVE-2024-6060 | whole record Sonatype | stated at publication 6.8, now states 9.3CVSS v4.0 · base scoreMediumCritical | Time to revision 1 days |
| Tue 25 Jun 2024· 1 change | ||||
| 2024-06-25 | CVE-2024-5806 | whole record ProgressSoftware | stated at publication 7.4, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Fri 3 May 2024· 1 change | ||||
| 2024-05-03 | CVE-2023-0118 | whole record redhat | stated at publication 8.0, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 226 days |
| Tue 23 Apr 2024· 1 change | ||||
| 2024-04-23 | CVE-2024-4040 | whole record directcyber | stated at publication 7.7, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 1 days |
| Wed 17 Apr 2024· 1 change | ||||
| 2024-04-17 | CVE-2024-3871 | whole record ONEKEY | stated at publication 7.2, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 1 days |
| Mon 15 Apr 2024· 1 change | ||||
| 2024-04-15 | CVE-2024-29844 | whole record directcyber | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Wed 13 Mar 2024· 1 change | ||||
| 2024-03-13 | CVE-2024-2044 | whole record PostgreSQL | stated at publication 4.6, now states 9.9CVSS v3.1 · base scoreMediumCritical | Time to revision 6 days |
| Mon 29 Jan 2024· 1 change | ||||
| 2024-01-29 | CVE-2023-6816 | whole record redhat | stated at publication 7.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 11 days |
| Wed 10 Jan 2024· 2 changes | ||||
| 2024-01-10 | CVE-2023-42000 | whole record tenable | stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 44 days |
| 2024-01-10 | CVE-2023-41999 | whole record tenable | stated at publication 8.3, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 44 days |
| Tue 2 Jan 2024· 1 change | ||||
| 2024-01-02 | CVE-2023-3961 | whole record redhat | stated at publication 6.5, now states 9.1CVSS v3.1 · base scoreMediumCritical | Time to revision 60 days |
| Thu 7 Dec 2023· 1 change | ||||
| 2023-12-07 | CVE-2023-45849 | whole record Perforce | stated at publication 8.5, now states 9.0CVSS v3.1 · base scoreHighCritical | Time to revision 29 days |
| Wed 18 Oct 2023· 1 change | ||||
| 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 |
| Fri 6 Oct 2023· 1 change | ||||
| 2023-10-06 | CVE-2023-5053 | whole record Fluid Attacks | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 8 days |
| Tue 26 Sep 2023· 1 change | ||||
| 2023-09-26 | CVE-2023-36845 | whole record juniper | stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 40 days |
| Wed 26 Jul 2023· 4 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-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 |
| Wed 12 Jul 2023· 1 change | ||||
| 2023-07-12 | CVE-2023-0090 | whole record Proofpoint | stated at publication 8.1, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 127 days |
| Fri 7 Jul 2023· 1 change | ||||
| 2023-07-07 | CVE-2023-35987 | whole record icscert | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 1 days |
| Thu 6 Apr 2023· 1 change | ||||
| 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 |
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 →