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 26 Oct 2023· 1 change | ||||
| 2023-10-26 | CVE-2023-40254 | whole record krcert | stated at publication 7.4, now states 7.5CVSS v3.1 · base scoreHighHighOriginal value first replaced 2023-08-17; this value first seen 2023-10-26. | Time to revision 6 days |
| Wed 25 Oct 2023· 1 change | ||||
| 2023-10-25 | CVE-2023-26570 | whole record TML | stated at publication 9.8, now states 7.5CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Mon 23 Oct 2023· 1 change | ||||
| 2023-10-23 | CVE-2023-39193 | whole record redhat | stated at publication 5.1, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 14 days |
| Sun 22 Oct 2023· 1 change | ||||
| 2023-10-22 | CVE-2023-2091 | whole record VulDB | stated at publication 5.3, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 190 days |
| Thu 19 Oct 2023· 2 changes | ||||
| 2023-10-19 | CVE-2023-45159 | whole record 1E | stated at publication 7.3, now states 8.4CVSS v3.1 · base scoreHighHigh | Time to revision 14 days |
| 2023-10-19 | CVE-2023-45160 | whole record 1E | stated at publication 10.0, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 14 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 |
| 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 |
| Fri 13 Oct 2023· 4 changes | ||||
| 2023-10-13 | CVE-2023-4828 | whole record Proofpoint | stated at publication 8.8, now states 6.4CVSS v3.1 · base scoreHighMedium | Time to revision 30 days |
| 2023-10-13 | whole record Proofpoint | stated at publication 5.9, now states 4.8CVSS v3.1 · base scoreMediumMedium | Time to revision 30 days | |
| 2023-10-13 | CVE-2023-4802 | same vendor as the line above | same change as the line above | Time to revision 30 days |
| 2023-10-13 | CVE-2023-4803 | same vendor as the line above | same change as the line above | Time to revision 30 days |
| 2023-10-13 | CVE-2023-3589 | whole record 3DS | stated at publication 6.4, now states 6.8CVSS v3.1 · base scoreMediumMedium | Time to revision 4 days |
| Thu 12 Oct 2023· 1 change | ||||
| 2023-10-12 | CVE-2023-29338 | whole record microsoft | stated at publication 5.0, now states 6.6CVSS v3.1 · base scoreMediumMedium | Time to revision 156 days |
| Fri 6 Oct 2023· 33 changes | ||||
| 2023-10-063 commits | whole record Fluid Attacks | stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMediumBranches and original-value intervals are stated on each row. | Time to revision 6 to 7 days | |
| 2023-10-06 | CVE-2023-43728 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43729 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43730 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43731 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43732 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43733 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43734 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2023-10-06 | CVE-2023-43735 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 24 more rows in this change are not listed here. Open all 32 rows → | ||||
| 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 3 Oct 2023· 3 changes | ||||
| 2023-10-03 | CVE-2023-22283 | whole record f5 | stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 244 days |
| 2023-10-03 | CVE-2023-43740 | whole record Fluid Attacks | stated at publication 9.1, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 5 days |
| 2023-10-03 | CVE-2023-5111 | whole record Fluid Attacks | stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium | Time to revision 3 days |
| Mon 2 Oct 2023· 1 change | ||||
| 2023-10-02 | CVE-2023-0809 | whole record eclipse | stated at publication 10.0, now states 5.8CVSS v3.1 · base scoreCriticalMedium | Time to revision 0 days |
| Thu 28 Sep 2023· 1 change | ||||
| 2023-09-28 | CVE-2023-3567 | whole record redhat | stated at publication 6.7, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 66 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 |
| 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 |
| 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 |
| Mon 18 Sep 2023· 1 change | ||||
| 2023-09-18 | CVE-2023-4387 | whole record redhat | stated at publication 6.6, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 33 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 |
| Thu 14 Sep 2023· 8 changes | ||||
| 2023-09-142 commits | whole record SolarWinds | stated at publication 6.8, now states 7.2CVSS v3.1 · base scoreMediumHighBranches and original-value intervals are stated on each row. | Time to revision 50 days | |
| 2023-09-14 | CVE-2023-33225 | same vendor as the line above | same change as the line above | Time to revision 50 days |
| 2023-09-14 | CVE-2023-23842 | same vendor as the line above | same change as the line above | Time to revision 50 days |
| 2023-09-14 | CVE-2023-33229 | whole record SolarWinds | stated at publication 3.1, now states 3.5CVSS v3.1 · base scoreLowLow | Time to revision 50 days |
| 2023-09-14 | whole record SolarWinds | stated at publication 6.6, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 7 to 35 days | |
| 2023-09-14 | CVE-2023-35179 | same vendor as the line above | same change as the line above | Time to revision 35 days |
| 2023-09-14 | CVE-2023-40060 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2023-09-14 | CVE-2023-3622 | whole record SolarWinds | stated at publication 4.6, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 50 days |
| 2023-09-14 | CVE-2023-38235 | whole record adobe | stated at publication 7.8, now states 5.5CVSS v3.1 · base scoreHighMedium | Time to revision 35 days |
| 2023-09-14 | CVE-2023-38207 | whole record adobe | stated at publication 5.3, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 36 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 |
| Wed 6 Sep 2023· 1 change | ||||
| 2023-09-06 | CVE-2023-41040 | whole record GitHub_M | stated at publication 5.3, now states 4.0CVSS v3.1 · base scoreMediumMedium | Time to revision 7 days |
| Fri 25 Aug 2023· 11 changes | ||||
| 2023-08-25 | CVE-2023-40031 | whole record GitHub_M | stated at publication 8.6, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2023-08-25 | whole record GitHub_M | stated at publication 6.3, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days | |
| 2023-08-25 | CVE-2023-40036 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2023-08-25 | CVE-2023-40164 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2023-08-25 | CVE-2023-22815 | whole record WDC PSIRT | stated at publication 6.0, now states 6.2CVSS v3.1 · base scoreMediumMedium | Time to revision 56 days |
| 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 |
| 2023-08-25 | CVE-2023-3262 | whole record trellix | stated at publication 6.2, now states 6.7CVSS v3.1 · base scoreMediumMedium | Time to revision 11 days |
| 2023-08-25 | CVE-2023-3264 | whole record trellix | stated at publication 8.4, now states 6.7CVSS v3.1 · base scoreHighMedium | Time to revision 11 days |
| Tue 22 Aug 2023· 1 change | ||||
| 2023-08-22 | CVE-2023-0871 | whole record OpenNMS | stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2023-08-17; this value first seen 2023-08-22. | Time to revision 6 days |
| Mon 21 Aug 2023· 3 changes | ||||
| 2023-08-21 | CVE-2023-29360 | whole record microsoft | stated at publication 7.8, now states 8.4CVSS v3.1 · base scoreHighHigh | Time to revision 69 days |
| 2023-08-21 | CVE-2023-40252 | whole record krcert | stated at publication 7.7, now states 6.0CVSS v3.1 · base scoreHighMedium | Time to revision 4 days |
| 2023-08-21 | CVE-2023-40253 | whole record krcert | stated at publication 4.4, now states 6.0CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-08-17; this value first seen 2023-08-21. | Time to revision 6 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 9 Aug 2023· 1 change | ||||
| 2023-08-09 | CVE-2023-26310 | whole record OPPO | stated at publication 9.1, now states 7.4CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Tue 8 Aug 2023· 2 changes | ||||
| 2023-08-08 | CVE-2023-36884 | whole record microsoft | stated at publication 0.0, now states 7.5CVSS v3.1 · base scoreNoneHighOriginal value first replaced 2023-07-31; this value first seen 2023-08-08. | Time to revision 20 days |
| 2023-08-08 | CVE-2023-3618 | whole record redhat | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 27 days |
| Thu 3 Aug 2023· 4 changes | ||||
| 2023-08-03 | whole record SolarWinds | stated at publication 6.8, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 8 days | |
| 2023-08-03 | CVE-2023-23843 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2023-08-03 | CVE-2023-23844 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2023-08-03 | CVE-2023-33224 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2023-08-03 | CVE-2023-33231 | whole record SolarWinds | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 16 days |
| Wed 2 Aug 2023· 1 change | ||||
| 2023-08-02 | CVE-2023-25841 | whole record Esri | stated at publication 4.8, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 11 days |
| Tue 1 Aug 2023· 7 changes | ||||
| 2023-08-01 | CVE-2023-31427 | whole record brocade | stated at publication 5.3, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 0 days |
| 2023-08-01 | CVE-2023-28261 | whole record microsoft | stated at publication 6.1, now states 5.7CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-06-17; this value first seen 2023-08-01. | Time to revision 50 days |
| 2023-08-01 | CVE-2023-24936 | whole record microsoft | stated at publication 8.1, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 48 days |
| 2023-08-01 | CVE-2023-32012 | whole record microsoft | stated at publication 6.3, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 49 days |
| 2023-08-01 | CVE-2023-32013 | whole record microsoft | stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 49 days |
| 2023-08-01 | CVE-2023-32020 | whole record microsoft | stated at publication 3.7, now states 5.6CVSS v3.1 · base scoreLowMedium | Time to revision 49 days |
| 2023-08-01 | CVE-2023-33144 | whole record microsoft | stated at publication 5.0, now states 6.6CVSS v3.1 · base scoreMediumMedium | Time to revision 49 days |
| Mon 31 Jul 2023· 3 changes | ||||
| 2023-07-31 | CVE-2023-0009 | whole record palo_alto | stated at publication 6.7, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 47 days |
| 2023-07-31 | CVE-2023-28013 | whole record HCL | stated at publication 6.6, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 5 days |
| 2023-07-31 | CVE-2023-32712 | whole record Splunk | stated at publication 3.4, now states 8.6CVSS v3.1 · base scoreLowHigh | Time to revision 60 days |
| Thu 27 Jul 2023· 1 change | ||||
| 2023-07-27 | CVE-2023-28012 | whole record HCL | stated at publication 6.6, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 0 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 |
| Tue 25 Jul 2023· 1 change | ||||
| 2023-07-25 | CVE-2023-3897 | whole record 42Gears | stated at publication 3.7, now states 4.8CVSS v3.1 · base scoreLowMedium | Time to revision 0 days |
| Thu 20 Jul 2023· 1 change | ||||
| 2023-07-20 | CVE-2023-24568 | whole record dell | stated at publication 7.4, now states 5.0CVSS v3.1 · base scoreHighMedium | Time to revision 51 days |
| Mon 17 Jul 2023· 6 changes | ||||
| 2023-07-17 | CVE-2023-31194 | whole record talos | stated at publication 4.0, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 12 days |
| 2023-07-17 | CVE-2023-27390 | whole record talos | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 12 days |
| 2023-07-17 | CVE-2023-24019 | whole record talos | stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 11 days |
| 2023-07-17 | whole record talos | stated at publication 8.3, now states 4.7CVSS v3.1 · base scoreHighMedium | Time to revision 11 days | |
| 2023-07-17 | CVE-2023-24496 | same vendor as the line above | same change as the line above | Time to revision 11 days |
| 2023-07-17 | CVE-2023-24497 | same vendor as the line above | same change as the line above | Time to revision 11 days |
| 2023-07-17 | CVE-2023-23571 | whole record talos | stated at publication 8.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 11 days |
| Fri 14 Jul 2023· 2 changes | ||||
| 2023-07-14 | CVE-2023-30990 | whole record ibm | stated at publication 5.6, now states 8.6CVSS v3.1 · base scoreMediumHigh | Time to revision 11 days |
| 2023-07-14 | CVE-2023-35348 | whole record microsoft | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 3 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 |
| Tue 11 Jul 2023· 1 change | ||||
| 2023-07-11 | CVE-2023-25910 | whole record siemens | stated at publication 9.9, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Time to revision 28 days |
| Mon 10 Jul 2023· 1 change | ||||
| 2023-07-10 | CVE-2023-3389 | whole record Google | stated at publication 5.5, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 12 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 Jul 2023· 1 change | ||||
| 2023-07-06 | CVE-2023-3529 | whole record VulDB | stated at publication 4.3, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Mon 3 Jul 2023· 1 change | ||||
| 2023-07-03 | CVE-2023-25515 | whole record nvidia | stated at publication 7.1, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 10 days |
| Fri 23 Jun 2023· 1 change | ||||
| 2023-06-23 | CVE-2023-28043 | whole record dell | stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 22 days |
| Sat 17 Jun 2023· 5 changes | ||||
| 2023-06-17 | CVE-2023-23416 | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 94 days |
| 2023-06-17 | CVE-2023-24856 | whole record microsoft | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 94 days |
| 2023-06-17 | CVE-2023-24921 | whole record microsoft | stated at publication 4.1, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 94 days |
| 2023-06-17 | CVE-2023-28288 | whole record microsoft | stated at publication 6.5, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 66 days |
| 2023-06-17 | CVE-2023-28301 | whole record microsoft | stated at publication 4.2, now states 3.7CVSS v3.1 · base scoreMediumLow | Time to revision 66 days |
| Fri 16 Jun 2023· 1 change | ||||
| 2023-06-16 | CVE-2023-2431 | whole record kubernetes | stated at publication 6.5, now states 3.4CVSS v3.1 · base scoreMediumLow | Time to revision 0 days |
| Wed 14 Jun 2023· 2 changes | ||||
| 2023-06-14 | CVE-2023-34251 | whole record GitHub_M | stated at publication 9.1, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 days |
| 2023-06-14 | CVE-2023-34252 | whole record GitHub_M | stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh | 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 →